I'm using the Cassandra 2.0.9 with JAVA datastax driver.
I'm running the tests in a cluster with 3 nodes, RF=3 and CL=ALL for each
operation.
I have a Column family filled with some keys (for example 'a' and 'b').
When this keys are deleted and inserted hereafter, sporadically this keys
On Wed, Sep 17, 2014 at 11:55 AM, Sávio S. Teles de Oliveira
savio.te...@cuia.com.br wrote:
I'm using the Cassandra 2.0.9 with JAVA datastax driver.
I'm running the tests in a cluster with 3 nodes, RF=3 and CL=ALL for each
operation.
I have a Column family filled with some keys (for example
Make sure your clocks are synced. If they aren't, the writetime that
determines the most recent value will be incorrect.
On Wed, Sep 17, 2014 at 11:58 AM, Robert Coli rc...@eventbrite.com wrote:
On Wed, Sep 17, 2014 at 11:55 AM, Sávio S. Teles de Oliveira
savio.te...@cuia.com.br wrote:
I'm
Could you be experiencing
https://issues.apache.org/jira/browse/CASSANDRA-7801 ?
On Wed, Sep 17, 2014 at 2:09 PM, Jonathan Haddad j...@jonhaddad.com wrote:
Make sure your clocks are synced. If they aren't, the writetime that
determines the most recent value will be incorrect.
On Wed, Sep
The clocks are synced.
Could you be experiencing
https://issues.apache.org/jira/browse/CASSANDRA-7801 ?
Yes, its similar Philip. How can I solve this problem?
2014-09-17 16:16 GMT-03:00 Philip Thompson philip.thomp...@datastax.com:
Could you be experiencing
Philip, I'm not using IF NOT EXISTS on insert command.
2014-09-17 16:51 GMT-03:00 Sávio S. Teles de Oliveira
savio.te...@cuia.com.br:
The clocks are synced.
Could you be experiencing
https://issues.apache.org/jira/browse/CASSANDRA-7801 ?
Yes, its similar Philip. How can I solve this
On 17 Sep 2014, at 20:55, Sávio S. Teles de Oliveira savio.te...@cuia.com.br
wrote:
I'm using the Cassandra 2.0.9 with JAVA datastax driver.
I'm running the tests in a cluster with 3 nodes, RF=3 and CL=ALL for each
operation.
I have a Column family filled with some keys (for example 'a'
Perhaps you're seeing this:
https://issues.apache.org/jira/browse/CASSANDRA-6178
TL;DR: rapid deletes and inserts of the same key may use the same
timestamp, in which case the delete wins. Specifying the timestamp
explicitly in the CQL query is a good workaround. Alternatively, other
drivers