cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Cassandra Wiki] Update of "WritePathForUsers" by MichaelEdge
Date Wed, 02 Dec 2015 06:02:52 GMT
Dear Wiki user,

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

The "WritePathForUsers" page has been changed by MichaelEdge:
https://wiki.apache.org/cassandra/WritePathForUsers?action=diff&rev1=32&rev2=33

  == The Local Coordinator ==
  The local coordinator receives the write request from the client and performs the following:
   1. Firstly, the local coordinator determines which nodes are responsible for storing the
data:
-  * The first replica is chosen based on hashing the primary key using the Partitioner; Murmur3Partitioner
is the default.
+   * The first replica is chosen based on hashing the primary key using the Partitioner;
Murmur3Partitioner is the default.
-  * Other replicas are chosen based on the replication strategy defined for the keyspace.
In a production cluster this is most likely the NetworkTopologyStrategy.
+   * Other replicas are chosen based on the replication strategy defined for the keyspace.
In a production cluster this is most likely the NetworkTopologyStrategy.
   1. The local coordinator determines whether the write request would modify an associated
materialized view. 
  === If write request modifies materialized view ===
  When using materialized views it’s important to ensure that the base table and materialized
view are consistent, i.e. all changes applied to the base table MUST be applied to the materialized
view. Cassandra uses a two-stage batch log process for this: 

Mime
View raw message