It doesn’t make a lot of sense to run Cassandra on a single machine
as you are losing the benefits of a system with no single point of
failure.
Your client sends a write request to a single, random Cassandra node. This node acts as a proxy and writes the data to the cluster. The cluster of nodes is stored as a “ring” of nodes and writes are replicated to N nodes using a replication placement strategy. With the RackAwareStrategy, Cassandra will determine the “distance” from the current node for reliability and availability purposes where “distance” is broken into three buckets: same rack as current node, same data center as current node, or a different data center. You configure Cassandra to write data to N nodes for redundancy and it will write the first copy to the primary node for that data, the second copy to the next node in the ring in another data center, and the rest of the copies to machines in the same data center as the proxy. This ensures that a single failure does not take down the entire cluster and the cluster will be available even if an entire data center goes offline.
So the write request goes from your client to a single random node, which sends the write to N different nodes according to the replication placement strategy. There are many edge cases here (nodes are down, nodes being added to the cluster, etc) which I won’t go into but the node waits for the N successes and then returns success to the client.
Each of those N nodes gets that write request in the form of a “RowMutation” message. The node performs two actions for this message:
There are several asynchronous operations which occur regularly:
refer
http://wiki.apache.org/cassandra/FAQ
http://www.cs.cornell.edu/projects/ladis2009/papers/lakshman-ladis2009.pdf
http://wiki.apache.org/cassandra/FrontPage
http://nosql.mypopescu.com/post/518121097/hbase-adobe-an-interview-with-adobe-saas
http://nosql.mypopescu.com/post/407159447/cassandra-twitter-an-interview-with-ryan-king
Your client sends a write request to a single, random Cassandra node. This node acts as a proxy and writes the data to the cluster. The cluster of nodes is stored as a “ring” of nodes and writes are replicated to N nodes using a replication placement strategy. With the RackAwareStrategy, Cassandra will determine the “distance” from the current node for reliability and availability purposes where “distance” is broken into three buckets: same rack as current node, same data center as current node, or a different data center. You configure Cassandra to write data to N nodes for redundancy and it will write the first copy to the primary node for that data, the second copy to the next node in the ring in another data center, and the rest of the copies to machines in the same data center as the proxy. This ensures that a single failure does not take down the entire cluster and the cluster will be available even if an entire data center goes offline.
So the write request goes from your client to a single random node, which sends the write to N different nodes according to the replication placement strategy. There are many edge cases here (nodes are down, nodes being added to the cluster, etc) which I won’t go into but the node waits for the N successes and then returns success to the client.
Each of those N nodes gets that write request in the form of a “RowMutation” message. The node performs two actions for this message:
- Append the mutation to the commit log for transactional purposes
- Update an in-memory Memtable structure with the change
There are several asynchronous operations which occur regularly:
- A “full” Memtable structure is written to a disk-based structure called an SSTable so we don’t get too much data in-memory only.
- The set of temporary SSTables which exist for a given ColumnFamily are merged into one large SSTable. At this point the temporary SSTables are old and can be garbage collected at some point in the future.
refer
http://wiki.apache.org/cassandra/FAQ
http://www.cs.cornell.edu/projects/ladis2009/papers/lakshman-ladis2009.pdf
http://wiki.apache.org/cassandra/FrontPage
http://nosql.mypopescu.com/post/518121097/hbase-adobe-an-interview-with-adobe-saas
http://nosql.mypopescu.com/post/407159447/cassandra-twitter-an-interview-with-ryan-king
No comments:
Post a Comment