Re:Look Before You Leap – The Coming Leap Second and AWS
by hillsarealiv3 on Tuesday May 19, 2015 @02:14AM
(#9568362)
The idea of spreading a leap second over a longer period is not unique to Google e.g. www.quadibloc.com/science/cal06.htm
The idea itself is actually rather obvious.
[ Parent
| on HN ]
Re:Look Before You Leap – The Coming Leap Second and AWS
by fanf2 on Tuesday May 19, 2015 @05:26AM
(#9568838)
See also Markus Kuhn's description of smoothed leap seconds from 2005:
https://www.cl.cam.ac.uk/~mgk25/time/utc-sls/
Re:Look Before You Leap – The Coming Leap Second and AWS
by a-priori on Tuesday May 19, 2015 @01:15PM
(#9571604)
The time-smearing technique reminds me of how the Erlang platform (ERTS) adjusts its internal timekeeping to changes in the system's clock. If the system's clock jumps, then Erlang makes its internal clock tick faster or slower than the system's clock by at most 1% in order to resynchronize.
Re:Look Before You Leap – The Coming Leap Second and AWS
by jpatokal on Tuesday May 19, 2015 @02:31AM
(#9568415)
Most good ideas are obvious in hindsight. ;) But AFAIK, Google was the first to do this live and in production by hacking NTP, which is (apparently?) the same as what Amazon is doing.
Re:Look Before You Leap – The Coming Leap Second and AWS
by chronial on Tuesday May 19, 2015 @05:27AM
(#9568843)
SAP Systems have been doing this for many, many years live and in production for DST adjustments. Not sure about leap seconds.
Re:Look Before You Leap – The Coming Leap Second and AWS
by RedNifre on Tuesday May 19, 2015 @11:17AM
(#9570717)
What? How does it make sense to spread DST adjustments over a long time?
Re:Look Before You Leap – The Coming Leap Second and AWS
by Namrog84 on Tuesday May 19, 2015 @01:00PM
(#9571510)
What if in a dst jump. It had. Pay namrog84 $100 at 1:30am. Then 2 rolls around and it's 1am again and now I get paid a second time. Win! But if dst was smeared over a day. This would be easily prevented.