Re:Is Redlock Safe? Reply to Redlock Analysis
by jsprogrammer on Tuesday February 09, 2016 @07:49PM
(#11070044)
Because you don't want the system to break.
Re:Is Redlock Safe? Reply to Redlock Analysis
by derefr on Tuesday February 09, 2016 @10:22PM
(#11070558)
But it wouldn't, because the surrounding infrastructure would be guaranteeing that. My point is that distributed systems engineers are assuming too few things about the hardware and OS. A much wider space of distributed algorithms become useful if you have full control over your stack.
Do you think NASA quibbles about how to make a perfect consensus bit-coding algorithm between the fault-tolerant processors of a mars probe? No; they just use hardware+firmware that provides a hard real-time platform, allowing the algorithm itself to be simple.
Re:Is Redlock Safe? Reply to Redlock Analysis
by baruch on Wednesday February 10, 2016 @03:25AM
(#11071394)
It doesn't require a VM pause to cause a system freeze, an SMI interrupt can do that as well.
It doesn't take a lot to have backwards time travel, NTP can do that for you as well in some bad configurations.
It's very hard to rely on time in a distributed system. If you want a simple algorithm just don't rely on time at all, use it for logs so a human can correlate things when debugging an issue but don't assume time will flow at the same rate for all systems. Do use a monotonic clock always for internal timers, time does move backwards in systems.
Personally, though, I don't see why it's so hard to just say "this distributed lock system requires that soft real-time guarantees can be made of the host platform. If the platform misses the algorithm's scheduling deadline, the system breaks. If the platform has no way of providing for a soft real-time deadline (because e.g. it's running in a VM that can be paused), the software will detect this and fail to start."