zlacker

[return to "Clocks Are Bad, Or, Welcome to the World of Distributed Systems"]
1. flavie+t2[view] [source] 2013-11-13 00:44:36
>>pharkm+(OP)
Distributed systems design aside, the core of the problem is that they relied on ntp (as they probably should), and in their case ntp was not working properly.
◧◩
2. global+or[view] [source] 2013-11-13 08:57:08
>>flavie+t2
Even if NTP had been working properly, you would not have clocks synchronised at the level of individual ticks - only to the level of time intervals. If two updates happened at roughly the same time, and fell into the same time interval, there would be no way to tell which one happened before the other. A paper by Cilia et al on timing of composite events in distributed event-based systems using NTP deals with this issue.
◧◩◪
3. Dylan1+zA[view] [source] 2013-11-13 12:12:55
>>global+or
But this is not a problem in many situations. Whereas successor writes failing within an entire 30 second span is a pretty big problem.
[go to top]