Re: neither 'nodetool repair' nor 'hinted hanoff/read repair' work for secondary indexes

Made a d-test for easier reproduction and created https://issues.apache.org/jira/browse/CASSANDRA-5223 On 1 February 2013 15:14, Alexei Bakanov russ...@gmail.com wrote: Hi again, Once started playing with CCM it's hard to stop, such a great tool. My issue with secondary indexes is following

Re: Secondary index query + 2 Datacenters + Row Cache + Restart = 0 rows

Zealand @aaronmorton http://www.thelastpickle.com On 1/02/2013, at 9:03 PM, Alexei Bakanov russ...@gmail.com wrote: Hello, I've found a combination that doesn't work: A column family that have a secondary index and caching='ALL' with data in two datacenters and I do a restart of the nodes

Secondary index query + 2 Datacenters + Row Cache + Restart = 0 rows

Hello, I've found a combination that doesn't work: A column family that have a secondary index and caching='ALL' with data in two datacenters and I do a restart of the nodes, then my secondary index queries start returning 0 rows. It happens when amount of data goes over a certain threshold, so I

neither 'nodetool repair' nor 'hinted hanoff/read repair' work for secondary indexes

Hi again, Once started playing with CCM it's hard to stop, such a great tool. My issue with secondary indexes is following: neither explicit 'nodetool repair' nor implicit 'hinted handoffs/read repairs' resolve inconsistencies in data I get from secondary indexes. I observe this for both one- and

multiple reducers with BulkOutputFormat on the same host

enough for a sessionId when we have multiple JVMs streaming from one physical host. We get the problem fixed by setting one reducer per machine in hadoop config, but it's not an option we want to deploy. Thanks, Alexei Bakanov

Re: multiple reducers with BulkOutputFormat on the same host

AM, Alexei Bakanov wrote: Hello, We see that BulkOutputFormat fails to stream data from multiple reduce instances that run on the same host. We get the same error messages that issue https://issues.apache.org/jira/browse/CASSANDRA-4223 tries to address. Looks like (ip-adress + in_out_flag

Re: TTL on SecondaryIndex Columns. A bug?

PM, Alexei Bakanov russ...@gmail.com wrote: Hi, We are having an issue with TTL on Secondary index columns. We get 0 rows in return when running queries on indexed columns that have TTL. Everything works fine with small amounts of data, but when we get over a ceratin threshold it looks like

Re: TTL on SecondaryIndex Columns. A bug?

defaults to ONE. Cheers - Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 18/12/2012, at 9:44 PM, Alexei Bakanov russ...@gmail.com wrote: Hi, We are having an issue with TTL on Secondary index columns. We get 0 rows

TTL on SecondaryIndex Columns. A bug?

settings. Best regards, Alexei Bakanov