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
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
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
Thanks, I'll give that a try.
Is there a way to do this without JMX? I wouldn't know now to run a JMX
console on my production servers without a graphical interface.
On Mon, Oct 7, 2013 at 3:29 PM, Michał Michalski mich...@opera.com wrote:
I had similar issue (reported many times here,
We use Jmxterm: http://wiki.cyclopsgroup.org/jmxterm
On 10/07/2013 07:53 AM, Tom van den Berge wrote:
Thanks, I'll give that a try.
Is there a way to do this without JMX? I wouldn't know now to run a
JMX console on my production servers without a graphical interface.
On Mon, Oct 7, 2013 at
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
