[181437] in North American Network Operators' Group
Re: REMINDER: LEAP SECOND
daemon@ATHENA.MIT.EDU (Tore Anderson)
Wed Jun 24 14:33:23 2015
X-Original-To: nanog@nanog.org
Date: Wed, 24 Jun 2015 20:33:13 +0200
From: Tore Anderson <tore@fud.no>
To: "Majdi S. Abbas" <msa@latt.net>
In-Reply-To: <20150624160500.GC7191@puck.nether.net>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
* Majdi S. Abbas
> On Wed, Jun 24, 2015 at 08:33:14AM +0200, Tore Anderson wrote:
> > Leap years and DST ladjustments have never caused us any major
> > issues. It seems these code paths are well tested and work fine.
>
> I've seen quite a few people that for whatever reason insist
> on running systems in local time zones struggle with the DST reverse
> step. It's not nearly as much of a non-issue as you claim.
Read again, and note the word "us". I am describing my and my
employer's experience with past DST changes and leap years, and those
have indeed been completely uneventful.
YMMV.
> > The leap second in 2012 however ... total and utter carnage.
> > Application servers, databases, etc. falling over like dominoes. All
> > hands on deck in the middle of the night to clean up. It took days
> > before we stopped finding broken stuff.
>
> "Total and utter carnage" is a bit of a stretch.
As above, I am speaking only about how the 2012 leap second went down
in our infrastructure. I stand by how I described the event.
Again, YMMV. If you plan on let your infrastructure deal with the
upcoming leap second head-on, I wish you the best of luck. Hopefully
all the bugs from 2012 have been fixed. I, however, certainly have no
intention of being the one to find out otherwise.
Tore
