You can connect to any node in the cluster to issue a query. For that request, it's called the coordinator. The coordinator will figure out which node to talk to. The DataStax native drivers can use what's called token aware queries, in that they'll connect to one of the nodes that owns the data, saving a network hop.
Your replication factor determines the number of nodes that will own the data. There is no concept of master/secondary here, all the replicas can accept reads & writes, and your writes will be replicated to all replicas at the consistency level provided (as per the earlier doc). Does that help? On Thu, Apr 30, 2015 at 5:09 AM Nikolay Tikhonov <tikhonovnico...@gmail.com> wrote: > Thank for your response! > I've read the documentation but some points aren't clear for me still. > Does Cassandra support read/write operation only from/to node which is > responsible for this partition (calculated by has)? > > 2015-04-29 22:43 GMT+03:00 Robert Coli <rc...@eventbrite.com>: > >> On Wed, Apr 29, 2015 at 8:56 AM, Nikolay Tikhonov < >> tikhonovnico...@gmail.com> wrote: >> >>> I try to understand how to Cassandra supports data consistency and >>> compare it with other distributed caches. >>> >> >> For the record, Cassandra is not a distributed cache. >> >> =Rob >> >> >
