Search restored after leap second bug

Translate this post

At midnight UTC on July 1, Wikimedia’s search cluster stopped working. A “leap second” inserted by the NTP daemon at that time caused Java processes to lock up, including our Lucene search system. The same bug affected many other websites. Our engineers restored service in less than two hours.
Leap seconds are added to our clocks once every few years so that the sun will be directly overhead of the Royal Observatory in Greenwich at precisely 12:00. Some people believe that the desire to keep these two time standards synchronised is anachronistic, and that it would be better to let them drift apart for 600 years and then add a single “leap hour”. I’m sure many computer engineers would breathe a sigh of relief if such a change were implemented.
Tim Starling, Lead Platform Architect

Archive notice: This is an archived post from, which operated under different editorial and content guidelines than Diff.

Can you help us translate this article?

In order for this article to reach as many people as possible we would like your help. Can you translate this article to get the message out?

Inline Feedbacks
View all comments

Apparently a lot of websites experienced this problem. Glad to see you guys got it fixed. I would have been completely lost if it happend to my website.

[…] : La Fondation ne rejoindra pas l’Internet Defense League ■ La fonction de recherche ne fonctionnait plus sur Wikimedia à cause de la seconde intercalaire ■ Vous pouvez encore vous exprimer pour ou […]

Google has a way to avoid this bug, named “leap smear”:
But this maybe not help by java.