[181438] in North American Network Operators' Group
Re: REMINDER: LEAP SECOND
daemon@ATHENA.MIT.EDU (Matthew Huff)
Wed Jun 24 14:47:21 2015
X-Original-To: nanog@nanog.org
From: Matthew Huff <mhuff@ox.com>
To: Tore Anderson <tore@fud.no>
Date: Wed, 24 Jun 2015 18:47:16 +0000
In-Reply-To: <20150624203313.431e9267@envy.fud.no>
Cc: nanog2 <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Does anyone know what the latest that we can run our NTP servers and not di=
stribute the LEAP_SECOND flag to the NTP clients?
> On Jun 24, 2015, at 2:33 PM, Tore Anderson <tore@fud.no> wrote:
>=20
> * Majdi S. Abbas
>=20
>> 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.
>>=20
>> 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.
>=20
> 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.
>=20
> YMMV.
>=20
>>> 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.
>>=20
>> "Total and utter carnage" is a bit of a stretch.
>=20
> 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.
>=20
> 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.
>=20
> Tore
