Re:It’s time to leave the leap second in the past
by zeroimpl on Monday July 25, 2022 @10:20PM
(#32233514)
Seems a weird way to write an algorithm. Easier to rely on database locking and/or the obvious fact that if you have received some data telling you about an event having happened, then it has happened… Curious if there are any real reports where this caused issues?
[ Parent
| on HN ]
Re:It’s time to leave the leap second in the past
by rrss on Tuesday July 26, 2022 @09:42AM
(#32238147)
Refer to “Practical uses of synchronized clocks in distributed systems” for some info on algorithms like this.
https://dl.acm.org/doi/10.1145/112600.112601
Google spanner uses stuff like this with a clock called TrueTime. I don’t know how leap seconds / smearing is handled in that system.
Re:It’s time to leave the leap second in the past
by ncmncm on Monday July 25, 2022 @11:08PM
(#32233816)
If you have not heard of problems with time in distributed systems everywhere, maybe read up instead of guessing? There are literally thousands of papers on the topic, more every year. It is not considered solved.
Re:It’s time to leave the leap second in the past
by nemothekid on Tuesday July 26, 2022 @01:07AM
(#32234466)
If you have a distributed system that requires strict time synchronization why do you care if Google’s time is wrong? Surely if you need that level of synchronization you have your own implementation with gps clocks.
If you don’t, then you already have to deal with standard drift with ntp anyways so Googles time smear is the least of your problems
Re:It’s time to leave the leap second in the past
by ncmncm on Thursday July 28, 2022 @12:04AM
(#32260372)
One does not always have the luxury of systems operated entirely within one organization.
Re:It’s time to leave the leap second in the past
by nemothekid on Thursday July 28, 2022 @11:30AM
(#32265684)
If you don't have the luxury of managing all your systems within one organization, then time smear is the least of your problems. Day-to-day ntp drift alone will be a bigger problem.
Re:It’s time to leave the leap second in the past
by zeroimpl on Tuesday July 26, 2022 @12:17AM
(#32234188)
But where are the reports/blog posts from the thousands of companies using these algorithms that ran into performance problems the last few times cloud providers used time smearing? I’ve done some searching and can’t find any, which suggests this is mostly a theoretical issue.
Yes I could come up with an algorithm where this is a problem, but in most cases I’d favor a solution that doesn’t depend on separate systems having clocks perfectly in sync.