News for hackers. Stuff that matters.
Re:Is Redlock Safe? Reply to Redlock Analysis by Domenic_S on Tuesday February 09, 2016 @12:27PM (#11066982)
> I'm not even going to touch his argument that using system clocks in a distributed locking algorithm is safe...

He's using it relatively, ie. if (stop time - start time <= $got_lock_fast_enough) { continue... } Is this not legit?

Re:Is Redlock Safe? Reply to Redlock Analysis by carllerche on Tuesday February 09, 2016 @12:42PM (#11067094)
What if the system freezes between reading the current time from the hardware and the stead_time function returning?

In short, you CANNOT rely on time in any way shape or form for safety. You can only use it as advice & to get liveliness.

Martin's point is that Redlock pays the cost of other safe locking algorithms w/o the benefit of safety.

Re:Is Redlock Safe? Reply to Redlock Analysis by jodah on Tuesday February 09, 2016 @04:00PM (#11068710)
This, usually. It's fair to point out that very specialized clocks, such as Google uses with Spanner, can allow you to achieve some consistency without coordination/locks, but for pretty much anyone else the rule you stated very much applies.
Re:Is Redlock Safe? Reply to Redlock Analysis by newman314 on Tuesday February 09, 2016 @05:03PM (#11069160)
FWIW, I went digging for more recent info about TrueTime and found the following.

http://www.cse.buffalo.edu/~demirbas/publications/augmentedT...

Re:Is Redlock Safe? Reply to Redlock Analysis by pygy_ on Tuesday February 09, 2016 @12:31PM (#11067014)
In a virtualized environment, system time and wall clock time can vary widely. Imagine a VM that's paused and restored.
Re:Is Redlock Safe? Reply to Redlock Analysis by derefr on Tuesday February 09, 2016 @06:43PM (#11069743)
I would assume that introducing a VM that has "time-travelled" (especially the restore-from-previous-state case someone mentioned above) into a distributed system would inherently break that distributed system, no matter what it's doing. It's a really crazy thing to do, much crazier than a regular network partition.

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."

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.

Re:Is Redlock Safe? Reply to Redlock Analysis by ahoka on Wednesday February 10, 2016 @06:56AM (#11072136)
I have seen SMI pauses for almost 5 seconds!