News for hackers. Stuff that matters.
Re:It’s time to leave the leap second in the past by ncmncm on Monday July 25, 2022 @05:28PM (#32231173)
They will be wrong all day long, not just for one second. AWS will be, too, evidently.

Few others will do anything so idiotic.

Re:It’s time to leave the leap second in the past by guipsp on Monday July 25, 2022 @05:44PM (#32231337)
They will be wrong by at most one second. And being wrong doesn't even matter, as long as everyone (or rather, all your servers) agree.
Re:It’s time to leave the leap second in the past by fanf2 on Monday July 25, 2022 @06:25PM (#32231757)
At most half a second, in the middle of the smear at midnight when the leap second is applied.

The Facebook smear is asymmetrical so it starts off 1 second off just after the leap second, and subsequently corrects itself.

[ The reason Google and Amazon use a linear smear is because NTP clients try to measure the rate difference between their local clock and the reference clocks; if that is different every time the NTP client queries its servers, it will have trouble locking on and accurately matching the smear curve. You can mitigate this somewhat by fixing a higher NTP query frequency, but that’s a heavy-handed fix for an engineering mistake. ]

Re:It’s time to leave the leap second in the past by lifeisstillgood on Tuesday July 26, 2022 @02:59AM (#32235230)
They are "wrong" technically but they won't be "wrong" more than a packet getting routed transatlantic would be - so if I send two packets from my laptop in London - one to AWS in London during the smear and one to another laptop in NYC, and timestamped the packets arrivals, the time stamps would likely be similar. Yes "wrong" but if it's a problem then it's a problem you have with speed of light. The answer is to find a different / reliable method of ordering.
Re:It’s time to leave the leap second in the past by staticassertion on Monday July 25, 2022 @06:04PM (#32231531)
What are the practical issues with potentially being wrong for one day by at most one second?
Re:It’s time to leave the leap second in the past by a9h74j on Monday July 25, 2022 @06:13PM (#32231631)
I assume finance and control systems to start. I might be helpful to have a fallback time-ordering algorithm not dependent upon one monotonic clock, but then you might have a rarely-used fallback to have bugs in, I imagine.
Re:It’s time to leave the leap second in the past by Too on Tuesday July 26, 2022 @02:02AM (#32234830)
What are the practical issues for finance and control systems?
Re:It’s time to leave the leap second in the past by denton-scratch on Tuesday July 26, 2022 @05:51AM (#32236255)
For finance, it matters what order events occur in. I've never messed with control systems, but I suppose similar issues arise.
Re:It’s time to leave the leap second in the past by Too on Tuesday July 26, 2022 @08:12AM (#32237211)
Control systems, or any form of embedded safety critical system, use monotonic clocks where calendar time is a complete non-issue.

Ordering of events, on what scale are we talking here? If it’s just within a transactional database there are multitude of ways to do it. Even distributed dbs have such features without relying on perfect time. If you are looking at a spanner style db you need a lot more guarantees than “I just used the time my cloud provider assigned to my vm”, plus being in sync only matters within your own cluster?

Re:It’s time to leave the leap second in the past by GoblinSlayer on Tuesday July 26, 2022 @07:45AM (#32236978)
Ordering can be solved by a mutex.
Re:It’s time to leave the leap second in the past by a9h74j on Tuesday July 26, 2022 @05:02PM (#32243964)
I was thinking of more distributed control systems, particularly where testing for edge cases might be difficult and rare, and rigorous methods (did Lamport solve distributed mutex?) are probably off the radar in terms of culture.
Re:It’s time to leave the leap second in the past by GoblinSlayer on Wednesday July 27, 2022 @09:25AM (#32250116)
Any forum is a distributed system of a server and clients that agree with each other on order of user posts.