Bizur: A Key-Value Consensus Algorithm for Scalable File-Systems

Re:Bizur: A Key-Value Consensus Algorithm for Scalable File-... by rystsov on Thursday March 09, 2017 @02:21AM (#13827688)

> If you can sacrifice more, you can get Single Paxos

What do you mean? Single Decree Paxos is linearizable so it's consistent. When the multi-key updates are necessary - they can be implemented with client-side transactions such as 2PC, RAMP or Percolator.

Even with Raft we in the same situation. Once the data overgrows the size of one machine we need to shard them. As a result some keys can live on different shards and we need cross shards transactions to do multi-key updates :)

[ Parent | on HN ]

Re:Bizur: A Key-Value Consensus Algorithm for Scalable File-... by ideal0227 on Thursday March 09, 2017 @03:02AM (#13827833)

Well... Why do you need 2PC if nothing is sacrificed? :)

If you choose things like Raft (or other RSM), you can get a consistent key space to do txn over keys.

For a metadata store like etcd, one RSM group is OK. Performance/availability is better than something requires 2PC.

For database systems, there are quite a few txns that can actually fall into one shard and can bypass 2PC.

Of course, it is highly depend on the workload and use cases.

[ Parent | on HN ]