News for hackers. Stuff that matters.

A comment on Paxos vs. Raft: Have we reached consensus on distributed consensus?. Parent comment

Re:Paxos vs. Raft: Have we reached consensus on distributed ... by tyingq on Friday July 16, 2021 @03:49PM (#27860464)
This makes sense to me. Very few of us have the resources to maintain, for example, the kind of globally synced (way beyond typical NTP) clock infrastructure that Google has (TrueTime[1]).

[1] https://cloud.google.com/spanner/docs/true-time-external-con...

[ Parent | on HN ]
Re:Paxos vs. Raft: Have we reached consensus on distributed ... by gravypod on Friday July 16, 2021 @05:32PM (#27861485)
If you want to know just how hard this can be with bare metal that you control, take a look at this: https://signalsandthreads.com/clock-synchronization/
[ Parent | on HN ]
Re:Paxos vs. Raft: Have we reached consensus on distributed ... by jeffbee on Friday July 16, 2021 @06:43PM (#27862021)
On the other hand, if you run in Google Compute Engine you get accurate clock discipline for free.
[ Parent | on HN ]
Re:Paxos vs. Raft: Have we reached consensus on distributed ... by electricshampo1 on Friday July 16, 2021 @08:16PM (#27862583)
This is just best effort on google's end right? Don't think anything is documented/guaranteed such that you would be able to, for ex. rely on it like spanner's use of true time.
[ Parent | on HN ]
Re:Paxos vs. Raft: Have we reached consensus on distributed ... by jeffbee on Friday July 16, 2021 @09:28PM (#27862909)
Sure, you'd have to invent the rest, but TrueTime isn't about having perfect clocks, it's about estimating the error of your peer's clocks. Having a reasonable platform clock is a good starting point, and addresses the problems discussed in the Jane Street article.
[ Parent | on HN ]