Sounds like https://issues.apache.org/jira/browse/CASSANDRA-2870 to me. You can disable the dynamic snitch as a workaround, or use a different consistencylevel.
On Mon, Jul 11, 2011 at 11:38 AM, Hefeng Yuan <hfy...@rhapsody.com> wrote: > Hi, > We're using Cassandra with 2 DC > - one OLTP Cassandra, 6 nodes, with RF3 > - the other is a Brisk, 3 nodes, with RF1 > We noticed that when I do a write-then-read operation on the Cassandra DC, > it fails with the following information (from cqlsh): > Unable to complete request: one or more nodes were unavailable. > - write: LOCAL_QUORUM, successful > - read: LOCAL_QUORUM, using the secondary indexed column, fail > Seems it's taking a long while working on this. When I retry the same query > after ~10 minutes, it succeeds actually. > Any help is appreciated. > Thanks, > Hefeng -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
