I think you might be seeing the issue reported in
https://issues.apache.org/jira/browse/CASSANDRA-6971
If that's the case, it looks like a fix will be in 2.0.7
Thanks,
Russ
On Tue, Apr 15, 2014 at 11:48 PM, Umut Kocasaraç wrote:
> Hi Olek,
>
> Could you solve the problem. Because we are exper
>
> If the commitlog is in periodic mode and the fsync happens every 10
> seconds, Cassandra is storing the stuff that needs to be sync'd somewhere
> for a period of 10 seconds. I'm talking about before it even hits any
> disk. This has to be in memory, correct?
The information you are referri
I did some quick testing to try and reproduce the issue you are seeing
(using 1.2.15). I wasn't able to get the same issue to happen though. You
are correct that normally the pre-existing values would be indexed and
searchable. You may want to search JIRA to see if anyone else has had the
issue, an
If you are using cqlsh, you can get a look at what's happening behind the
scenes by enabling tracing with 'tracing on;' before executing a query. In
this scenario you'll see 'Sending message to [ip address]' for each of the
replicas.
On Fri, Mar 7, 2014 at 5:44 PM, Jonathan Lacefield
wrote:
> B
