cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Cassandra Wiki] Update of "ArchitectureInternals" by JonathanEllis
Date Tue, 24 Nov 2009 19:12:12 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.

The "ArchitectureInternals" page has been changed by JonathanEllis.
The comment on this change is: link papers.


   * If a quorum read was requested, !StorageProxy waits for a majority of nodes to reply
and makes sure the answers match before returning.  Otherwise, it returns the data reply as
soon as it gets it, and checks the other replies for discrepancies in the background in !StorageService.doConsistencyCheck.
 This is called "read repair," and also helps achieve consistency sooner.
     * As an optimization, !StorageProxy only asks the closest replica for the actual data;
the other replicas are asked only to compute a hash of the data.
+ = Gossip =
+  * based on "Efficient reconciliation and flow control for anti-entropy protocols:"
+  * See ArchitectureGossip for more details
+ = Failure detection =
+  * based on "The Phi accrual failure detector:"
  = Further reading =
   * Cassandra's distribution is closely related to the one presented in Amazon's Dynamo paper.
 Read repair, adjustable consistency levels, hinted handoff, and other concepts are discussed
there.  This is required background material:
+  * Facebook's Cassandra team authored a paper on Cassandra for LADIS 09:
Most of the information there is applicable to Apache Cassandra (the main exception is the
integration of ZooKeeper).

View raw message