On Tue, Jan 24, 2012 at 9:57 AM, Peter Dijkshoorn
wrote:
> yeah, well main question remains then, is the node receiving the request
> from the client called the coordinator (even if it is not responsible
> for that key)?
Yes.
> Or will that node forward the call to the first responsible node who
yeah, well main question remains then, is the node receiving the request
from the client called the coordinator (even if it is not responsible
for that key)?
Or will that node forward the call to the first responsible node who
does the coordinating stuff? (as the cassandra and dynamo paper state)
Ouch :-) you were asking write ...
Well kind of similar
1. Coordinator calculates all nodes
2. If not enough (according to CL) nodes are alive it throughs unavailable
3. If nodes are down it writes and hh is enabled it writes a hint for that row
4. It sends write request to all nodes (including
Your first thought was pretty much correct:
1. The node which is called by the client is the coordinator
2. The coordinator determines the nodes in the ring which can handle the
request ordered by expected latency (via snitch). The coordinator may or may
not be part of these nodes
3. Given the c
Hi guys,
I got an architectural question about how a write operation flows
through the nodes.
As far as I understand now, a client sends its write operation to
whatever node it was set to use and if that node does not contain the
data for this key K, then this node forwards the operation to the
