News for hackers. Stuff that matters.
Re:Is Redlock Safe? Reply to Redlock Analysis by dsp1234 on Tuesday February 09, 2016 @02:11PM (#11067846)
What is the effect on the client of a VM live migration "pause"?

or daylight savings change?

or ntp updates which change the time?

Since the system clock can change relative to itself at any time, what effect does that have on the algorithm?

Re:Is Redlock Safe? Reply to Redlock Analysis by xorcist on Tuesday February 09, 2016 @03:13PM (#11068387)
Distributed time is tricky, but it depends on what the intended use is. Under normal operation it will only move forward, for example.

> VM live migration "pause"?

System clock will take a larger step than usual. It won't go backwards.

> daylight savings change?

None. System clock is UTC for a reason.

> ntp updates which change the time?

NTP only drifts the clock (under normal operation).

Re:Is Redlock Safe? Reply to Redlock Analysis by dsp1234 on Tuesday February 09, 2016 @04:14PM (#11068825)
Not that I think it effects your point, but just off the top of my head:

System clock will take a larger step than usual. It won't go backwards.

Assumes that checkpoint and restore to a previous time won't happen.

NTP only drifts the clock (under normal operation).

Unless it's a system like this. Note that this was pulled at about 1pm EST.

  Waiting for clock tick...
  ...got clock tick
  Time read from Hardware Clock: 2016/02/09 22:36:50
  Hw clock time : 2016/02/09 22:36:50 = 1455057410 seconds since 1969
  Tue 09 Feb 2016 02:36:50 PM PST  -1.038948 seconds
Under normal operation it will only move forward

'Under normal operation' is not really a high bar for distributed systems. After all, the network is reliable 'under normal operation' too.

Re:Is Redlock Safe? Reply to Redlock Analysis by Dylan16807 on Wednesday February 10, 2016 @03:00PM (#11075535)
Use CLOCK_MONOTONIC. Or you could make your client abort when the clock goes backwards.

If someone forks a VM from a running snapshot, you're screwed whether they mess with the clock or not.

Re:Is Redlock Safe? Reply to Redlock Analysis by SrslyJosh on Tuesday February 09, 2016 @04:56PM (#11069101)
> Assumes that checkpoint and restore to a previous time won't happen.

Or migration to a host whose clock is behind the original host's clock.

Re:Is Redlock Safe? Reply to Redlock Analysis by baruch on Wednesday February 10, 2016 @03:15AM (#11071372)
> NTP only drifts the clock (under normal operation).

That shouldn't be an assumption. NTP may jump the clock if the difference is too high, I've had it once that a system was connected to two different NTP servers and they each had a different clock and the system would jump the clock every now and then based on what NTP server it though was more correct.

Re:Is Redlock Safe? Reply to Redlock Analysis by dvirsky on Tuesday February 09, 2016 @02:19PM (#11067915)
I don't disagree, I'm just saying that time drift between nodes is not an issue with this algorithm. Also, using monotonic clock as antirez says he intends to in the post, will take care of most of these scenarios besides VM migration pauses.