为什么闰秒出现问题？ [英] Why Does the Leap Second Cause Problems?

问题描述

所以在这个时刻（但很有可能不久），Reddit，Meetup，Fark，LinkedIn，Yelp，4Chan都已经失败了。 Netflix显然也出了一段时间。

So at this moment (but most likely not for long) Reddit, Meetup, Fark, LinkedIn, Yelp, 4Chan are all down. Netflix apparently was out for a while too.

根据Reddit的推文，他们在2012年6月30日之前发生了与闰秒有关的问题： https://twitter.com/redditstatus/status/219244389044731904

According to Reddit's tweet, they are having issues relating to the Leap Second from 6/30/2012: https://twitter.com/redditstatus/status/219244389044731904

我们在PST下午5点有一些Java / Cassandra问题与闰秒
有关，我们正在尽快恢复服务。

"We are having some Java/Cassandra issues related to the leap second at 5pm PST. We're working as quickly as we can to restore service."

显然，影响其他网站的问题都与闰秒相关。

Apparently, the issues affecting the other sites are all related to a leap second issue.

在阅读关于 Leap秒的维基百科文章后，我认为我明白什么是飞跃秒是...但是我没有得到的是，如果不考虑闰秒，会发生什么样的怪异行为？当我们编写和配置服务器时，作为程序员如何准备闰秒？

After reading Wikipedia article on Leap seconds, I think I understand what leap seconds are... but what I don't get is what kind of weird behaviors can happen if leap second isn't accounted for? And how, as programmers, should we prepare for leap seconds when we code and configure servers?

我的意思是只有一秒钟不是吗？

I mean it's only one second isn't it?

推荐答案

某些Linux内核（2.6.29之前的版本）具有处理闰秒的问题，到它可能导致内核恐慌。其他Linux内核可能遭受活锁。这显然对系统有不利影响，因为它需要重新启动。

Certain Linux kernels (versions before 2.6.29) have issues handling leap seconds, to the point where it can cause a kernel panic. Other Linux kernels can suffer from a livelock. This obviously has detrimental effects for the system, given that it requires a reboot.

这里是关于此主题的ServerFault问题，因为它真的是一个Linux服务器问题。

Here's the related ServerFault question on this topic, since it's really a Linux server issue.

这篇关于为什么闰秒出现问题？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！