为什么闰秒会引起问题? [英] 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

我们遇到了一些与闰秒相关的 Java/Cas​​sandra 问题太平洋标准时间下午 5 点.我们正在尽快恢复服务."

"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.

在阅读了关于 闰秒 的维基百科文章后，我认为我了解闰秒是什么......但我不明白的是，如果不考虑闰秒，会发生什么样的奇怪行为?以及，作为程序员，我们在编写和配置服务器时应该如何准备闰秒?

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屋！