Nothing comes to mind.
I'd start by using sstable2json to see if the missing rows are in the
main data CF -- i.e., are they just unindexed, or are they missing
completely?
On Sun, May 15, 2011 at 4:33 PM, Wojciech Pietrzok <kosci...@gmail.com> wrote:
> Hello,
>
> I've noticed strange behaviour of Cassandra when using secondary indexes.
> There are 2 Data Centers, each with 2 nodes, RF=4, on all nodes
> Cassandra 0.7.5 is installed.
> When I connect to one of the nodes in DC1 and perform query using
> secondary indexes ("get ColumnFamily where column = 'foo'" in
> cassandra-cli) I always get correct number of rows returned, no matter
> which ConsistencyLevel is set.
> When I connect to one of the nodes in DC2 and perform same query using
> ConsistencyLevel LOCAL_QUORUM the results are correct. But using
> ConsistencyLevel ONE Cassandra doesn't return correct number of rows
> (it seems that most of the times there some of the rows are missing).
> Tried running nodetool repair, and nodetool scrub but this doesn't seem to
> help.
>
> What might the cause of such behaviour?
>
> --
> KosciaK
>
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
