2011/5/23 Jonathan Ellis :
>> It was installed as 0.7.2 and upgraded with each new official release.
>
> I bet that's the problem, then.
> https://issues.apache.org/jira/browse/CASSANDRA-2244 could cause
> indexes to not be updated for releases < 0.7.4. You'll want to
> rebuild the index.
>
>> By
On Mon, May 23, 2011 at 5:47 AM, Wojciech Pietrzok wrote:
> It was installed as 0.7.2 and upgraded with each new official release.
I bet that's the problem, then.
https://issues.apache.org/jira/browse/CASSANDRA-2244 could cause
indexes to not be updated for releases < 0.7.4. You'll want to
rebui
It was installed as 0.7.2 and upgraded with each new official release.
As I wrote in another message in this thread, now nodes are upgraded
to 0.7.6 but it still seems that one of the problematic nodes returns
inconsistent data.
By the way - is it possible to force the rebuild of the secondary
ind
I've already tried running nodetool repair severail times before but
it didn't seem to help.
Now I've upgraded Cassandra to 0.7.6, run nodetool scrub, and nodetool
repair (twice). One of the problematic nodes seems to return correct
results now. But the second one still returns inconsistent data.
Has this cluster always been on 0.7.5 or was it upgraded from an
earlier version?
On Thu, May 19, 2011 at 3:26 AM, Wojciech Pietrzok wrote:
> Just checked. Seems to be present in CF on all nodes (in both
> datacenters), but are not indexed correctly
>
> On each node I've used sstablekeys for all
I am wondering if running nodetool repair will help in anyway
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Inconsistent-results-using-secondary-indexes-between-two-DC-tp632p6382819.html
Sent from the cassandra-u...@incubator.apache.org
Just checked. Seems to be present in CF on all nodes (in both
datacenters), but are not indexed correctly
On each node I've used sstablekeys for all CF_NAME-f-XX-Data.db files.
In cassandra-cli I've (using node that behaves correctly) made query
get CF_NAME where foo = bar, got correct number of r
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 wrote:
> Hello,
>
> I've noticed strange behaviour of Cassandra when usin
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'
