Live data from Hacker News

A More Flexible Paxos

ssougou.blogspot.com

21–23 of 23 posts

Re: A More Flexible Paxos

#21
I'm not Paxos expert either, but I see some issues with the current post that are probably not correct / totally precise:

- That 7 or more nodes exhibit degraded performance, and that 5 is the sweet spot seems like a handy-wavy statement. I'd like to see numbers. And I believe those will be related more to implementation details rather than algorithmical limitations. Sure, with more nodes, communication overhead grows. But only a majority needs to agree, so there's no need to wait for the slowest node. Sure there's a sweet spot, but I wouldn't say it's exactly 5.

- Paxos does not perform leader election. There's indeed, no concept of a leader. There's only proposer, acceptor and learner. There's a leader concept in Multi-paxos, but that's a different story, and it's just a performance improvement, not a requirement.

- The original Paxos paper may be harder to understand, but "Paxos made Simple" is not. Probably easier to understand (IMVHO) than Raft's paper.

- The post assumes, as most Paxos implementations, that the three Paxos roles (proposer, acceptor and learner) are collapsed into a single node. They could be in different nodes. This may challenge some of the assumptions made about the "regular" Paxos algorithm.

- What the post proposes could probably be easily simulated with a varying number of proposers, acceptors and learners (like for instance having a lower number of acceptors than learners). This should result in the same benefits of the modified algorithm... but without modifying the algorithm. This is important, since original algorithm is proven mathematically.

Re: A More Flexible Paxos

#22
post #18
post #9

"With systems getting more and more distributed, the Paxos algorithm has been gaining popularity." Has it though? I feel like many of the new distributed systems I read about are Raft based consensus.

I think there is more talk on HN about Raft. It ended up in some new visible open source projects etcd, RethinkDB. Any major companies the size of Amazon or Google running on raft? As for Paxos I think Amazon, Google (Spanner), Microsoft? have all implemented Paxos based systems are built and in production for a while. Basho has made it part of their Riak database etc. I mean, sure if popular is just number of times…

> Any major companies the size of Amazon or Google running on raft?

Google's Container Engine runs Kubernetes, which uses etcd, which uses Raft.

Re: A More Flexible Paxos

#23
post #18

Earlier quoted context omitted.

I think there is more talk on HN about Raft. It ended up in some new visible open source projects etcd, RethinkDB. Any major companies the size of Amazon or Google running on raft? As for Paxos I think Amazon, Google (Spanner), Microsoft? have all implemented Paxos based systems are built and in production for a while. Basho has made it part of their Riak database etc. I mean, sure if popular is just number of times…

> Any major companies the size of Amazon or Google running on raft? Google's Container Engine runs Kubernetes, which uses etcd, which uses Raft.

It runs Kubernetes for its users to run on, but does Google run its search or ad stuff on it?
Post reply on HN