To the degree that this suggests that there is a "master" node for
each range, IMO it is a "bug" in the paper. (There are several of
these.) Certainly there are no master nodes in Cassandra.
On Fri, Sep 3, 2010 at 12:02 AM, Ying Tang wrote:
> In dynamo's paper ,it says:
> Each key, k, is assign
In dynamo's paper ,it says:
Each key, k, is assigned to a coordinator node .
The coordinator is in charge of the replication of the data items that fall
within its range.
On Fri, Sep 3, 2010 at 2:56 PM, Benjamin Black wrote:
> On Thu, Sep 2, 2010 at 8:19 PM, Ying Tang wrote:
> > Recently , i r
On Thu, Sep 2, 2010 at 8:19 PM, Ying Tang wrote:
> Recently , i read the paper about Cassandra again .
> And now i have some concepts about the reading and writing .
> We all know Cassandra uses NWR ,
> When read :
> the request ---> a random node in Cassandra .This node acts as a proxy ,and
> it
Hi Aaron
Thanks for your reply.
In you text , does the coordinator means the random client that user send
request to ?
Do you mean no matter how many W is assigned to , the data will copy on N
node ? Just the client will think this write action is successful when W
nodes are be written ?
Ps. The
AKAIK, For read the coordinator sends the request to the number of nodes specified in the RF. RR is kicked off on the coordinator node after the read has completed. There is no key coordinator, what would you do if it as down ? The first node in the list of replication nodes is considered special,
Recently , i read the paper about Cassandra again .
And now i have some concepts about the reading and writing .
We all know Cassandra uses NWR ,
When read :
the request ---> a random node in Cassandra .This node acts as a proxy ,and
it routes the request.
Here ,
1. the proxy node route this requ
