Hello ploxiln, to see systems with clocks jumping is indeed possible, I&#x27;ll make it more clear in my blog post, but basically it is possible with some effort to prevent this in general, but more specifically the Martin suggestion of using the monotonic time API <i>is a good one</i> and was already planned. It&#x27;s very hard to argue that the monotonic time jumps back and forth AFAIK, so I think it&#x27;s a credible system model. The monotonic API surely avoids a lot of pitfalls that you can have with gettimeofday() and the sysadmin poking the computer time in one way or the other (ntpd or manually).<p>About the ad-hoc logic, in this case I think the problem is actually that you want to accept only what already exists. For example there are important distributed systems papers where the assumption of <i>absolute time bound error</i> among processes is made, using GPS units. This is a much stronger system model (much more synchronous) compared to what I assume, yet this is regarded as acceptable. So you have to ask yourself if, regardless of the fact this idea is from me, if you think that a computer, using the monotonic clock API, can count relative time with a max percentage of error. Yes? Then it&#x27;s a viable system model.<p>About you linking to Aphyr, Sentinel was never designed in order to make Redis strongly consistent nor to to make it able to retain writes, I always analyzed the system for what it is: a failover solution that, mixed with the asynchronous replication semantics of Redis, has certain failure modes, that are considered to be fine for the intended use case of Redis. That is, it has just a few best-effort checks in order to try to minimize the data loss, and it has ways to ensure that only one configuration wins, eventually (so that there are no permanent split brain conditions after partitions heal) and nothing more.<p>To link at this I&#x27;m not sure what sense it makes. If you believe Redlock is broken, just state it in a rigorous form, and I&#x27;ll try to reply.<p>If you ask me to be rigorous while I&#x27;m trying to make it clear with facts what is wrong about Martin analysis, you should do the same and just use arguments, not hand waving about me being lame at DS. Btw in my blog post I&#x27;ll detail everything and show why I think Redlock is not affected by network unbound delays.