Tyler Hobbs <ty...@datastax.com> wrote: > On Fri, Jun 1, 2012 at 9:39 AM, Oleg Dulin <oleg.du...@gmail.com> wrote: > > Is my understanding correct that this is where cassandra is telling us it > can't accomplish something within that timeout value -- as opposed to > network timeout ? Where is it set ? > > That's correct. Basically, the coordinator sees that a replica has not > responded (or can not respond) before hitting a timeout. This is > controlled by rpc_timeout_in_ms in cassandra.yaml. > > -- > Tyler Hobbs > DataStax <<a href="http://datastax.com/";>http://datastax.com/</a>>
So if we are using random partitioner, and read consistency of one, what does that mean ? We have a 3 node cluster, use write / read consistency of one, replication factor of 3. Is the node we are connecting to try to proxy requests ? Wouldn't our configuration ensure all nodes have replicas ?
