HackerPapers

arXiv:1103.2408cs.DB

Using Paxos to Build a Scalable, Consistent, and Highly Available Datastore

Jun Rao, Eugene J. Shekita, Sandeep Tata

Abstract

Spinnaker is an experimental datastore that is designed to run on a large cluster of commodity servers in a single datacenter. It features key-based range partitioning, 3-way replication, and a transactional get-put API with the option to choose either strong or timeline consistency on reads. This paper describes Spinnaker's Paxos-based replication protocol. The use of Paxos ensures that a data partition in Spinnaker will be available for reads and writes as long a majority of its replicas are alive. Unlike traditional master-slave replication, this is true regardless of the failure sequence that occurs. We show that Paxos replication can be competitive with alternatives that provide weaker consistency guarantees. Compared to an eventually consistent datastore, we show that Spinnaker can be as fast or even faster on reads and only 5% to 10% slower on writes.

arXiv comments
VLDB2011
Journal reference
Proceedings of the VLDB Endowment (PVLDB), Vol. 4, No. 4, pp. 243-254 (2011)
DOI
Subjects
cs.DBDatabases cs.DCDistributed, Parallel, and Cluster Computing

On Hacker News

Linked by 2 identifiable commenters in 2 comments across 2 threads, from Mar 2016 to Sep 2024.

Comments linking this paper, per year.

Discussed in comments2 threads

    • Ah thank you. That is a good list although I personally dislike the "Paxos Made Moderately Complex" paper... I think it adds too many different roles for very little benefit. When implementing multi-Paxos for class, I used that paper and felt it was more trouble than it needed…

      prydtView on HNParent context

  1. How We Build Code at Netflix 1 comment

Submitted to Hacker News

Connected through shared HN threads, not inferred similarity or a recommendation.