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.
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.
Re:Look Before You Leap – The Coming Leap Second and AWS
by Terretta on Tuesday May 19, 2015 @08:39AM
(#9569572)
Google didn't come up with that first. I'm aware of a number companies with multiple data enters (my last co had 14 around the world) and coordinated logs or time sensitive services that used this technique.
I personally implemented it 12 years ago, to support (a) a kind of geo-balancing based on time coordinated spoofed DNS responses, and (b) time stamped URL token expiration validation, sensitive to seconds, across distributed datacenters. I got the idea from Microsoft Windows' ability to drift the clock back into sync.
Google has adopted or reinvented a lot, and gets credit because they have extra time and resources to publish.
// TBC, they also invented a lot. But not this one. Sibling comments point out other implementations predating Google as well.
Re:Look Before You Leap – The Coming Leap Second and AWS
by acqq on Tuesday May 19, 2015 @04:11AM
(#9568654)
It looks to me AWS is using the different algorithm. See my other comment here.
Re:Look Before You Leap – The Coming Leap Second and AWS
by jasonmp85 on Tuesday May 19, 2015 @02:05AM
(#9568342)
Agreed that they definitely should have given some credit. I was unfamiliar with the concept (and didn't even know the term). The AWS post raised more questions than it answered, but that Google one is excellent and coins a great term.
http://googleblog.blogspot.com.au/2011/09/time-technology-an...