The suggested fix to run a major compaction on the index column family unfortunately didn't help. Though, rebuilding the index (nodetool rebuild_index) fixed it.
This bug appears to be almost the same as https://issues.apache.org/jira/browse/CASSANDRA-5732, (and some of the related bugs mentioned there), but there's one difference: these bug reports all mention the use of caching "ALL" as the cause of the problems. However, the column families I'm having trouble with have caching "KEYS_ONLY". On Mon, Oct 7, 2013 at 6:37 PM, Janne Jalkanen <janne.jalka...@ecyrd.com>wrote: > > https://issues.apache.org/jira/browse/CASSANDRA-5732 > > There is now a reproducible test case. > > /Janne > > On Oct 7, 2013, at 16:29 , Michał Michalski <mich...@opera.com> wrote: > > I had similar issue (reported many times here, there's also a JIRA issue, > but people reporting this problem were unable to reproduce it). > > What I can say is that for me the solution was to run major compaction on > the index CF via JMX. To be clear - we're not talking about compacting the > CF that IS indexed (your CF), but the internal Cassandra's one, which is > responsible for storing index data. > > MBean you should look for looks like this: > > > org.apache.cassandra.db:type=IndexColumnFamilies,keyspace=<KS>,columnfamily=<CF>.<IDX> > > M. > > W dniu 07.10.2013 15:22, Tom van den Berge pisze: > > On a 2-node cluster with replication factor 2, I have a column family with > an index on one of the columns. > > Every now and then, I notice that a lookup of the record through the index > on node 1 produces the record, but the same lookup on node 2 does not! If I > do a lookup by row key, the record is found, and the indexed value is > there. > > > So as far as I can tell, the index on one of the nodes looses values, and > is no longer in sync with the other node, even though the replication > factor requires it. I typically repair these issues by storing the indexed > column value again. > > The indexed data is static data; it doesn't change. > > I'm running cassandra 1.2.3. I'm running a nodetool repair on each node > every day (although this does not fix this problem). > > This problem worries me a lot. I don't have a clue about the cause of it. > Any help would be greatly appreciated. > > > > Tom > > > -- Drillster BV Middenburcht 136 3452MT Vleuten Netherlands +31 30 755 5330 Open your free account at www.drillster.com
