Yikes my apologies. B is not the answer On Mar 7, 2014, at 8:24 PM, Russell Hatch <rha...@datastax.com> wrote:
If you are using cqlsh, you can get a look at what's happening behind the scenes by enabling tracing with 'tracing on;' before executing a query. In this scenario you'll see 'Sending message to [ip address]' for each of the replicas. On Fri, Mar 7, 2014 at 5:44 PM, Jonathan Lacefield <jlacefi...@datastax.com>wrote: > B is the answer > > > On Mar 7, 2014, at 7:35 PM, James Lyons <james.ly...@gmail.com> wrote: > > > > I'm wondering about the following scenario. > > > > Consider a cluster of nodes with replication say 3. > > When performing a read at "read one" consistency and lets say my client > isn't smart enough to route the request to the Cassandra node housing the > data at first. the contacted node acts as a coordinator and forwards the > request to: > > A) a node that houses the data and waits for a reply, possibly timesout > and re-issues to another in a failure or slow host scenario. > > or > > B) all (3) the nodes that house the data and returns after any one of > them replies. > > > > I'm hoping for B... anyone know for sure? >
