Here’s How Google Face Leap Seconds

On June 30, at 23:59:59 UTC, “leap seconds” (leap second) return true. So far, the addition of a second at a time around the world has been 26 times occur. The last in 2012.

It is very influential to the IT world. To that end, each company has its own way so as not to be confused internal system leap seconds.

One of Google. The search engine giant find practical methods and intelligent to accommodate leap seconds.

You do this by adding a fraction of a second to count time the system gradually, 20 hours before the leap seconds applies.

At the end of pencicilan, all leap seconds have tersematkan, and we are back in sync with the normal time, “said Google engineer Noah Maxwell and Michael Rothwell.

Anticipation Google is simpler than ever conducted in 2012. At that time, Google adopted a prevention method modified leap second unit time internet network or the Network Time Protocol (NTP).

Google added a few milliseconds for each NTP updates provided before the leap second occurs.

Countermeasures leap seconds, said Maxwell and Rothwell, very important that there be chaos fatal. Therefore, any system that relies on the playback time will be problematic if it is allowed.

The reason, almost all Google software is not designed to conform with leap seconds. But, with a smart method, Maxwell and Rothwell ensure Google ready for leap seconds.

This problem affects the distribution system. Each addition of a second can have a major impact for each time synchronization system.

Keep in mind, a leap second is a phenomenon that is intentional to eliminate the difference between the international time standard (UTC) by the time the actual rotation of the earth. Where, one day is not always the right amount to 24 hours.