You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Philip Thompson (JIRA)" <ji...@apache.org> on 2015/04/01 17:09:53 UTC

[jira] [Comment Edited] (CASSANDRA-9086) CAS precondition mismatch - row is still inserted

    [ https://issues.apache.org/jira/browse/CASSANDRA-9086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390760#comment-14390760 ] 

Philip Thompson edited comment on CASSANDRA-9086 at 4/1/15 3:09 PM:
--------------------------------------------------------------------

Are you able to reproduce this consistently? Do you know if the row existed or not beforehand? It will help us know if this is incorrectly overwriting data, or should be applying, but incorrectly reporting a failure.

What is the RF on the keyspace holding this table?


was (Author: philipthompson):
Are you able to reproduce this consistently? Do you know if the row existed or not beforehand? It will help us know if this is incorrectly overwriting data, or should be applying, but incorrectly reporting a failure.

> CAS precondition mismatch - row is still inserted
> -------------------------------------------------
>
>                 Key: CASSANDRA-9086
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9086
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Cassandra version 2.0.11
> 24 nodes in 4 datacenters (6 nodes per dc)
>            Reporter: Roger Schildmeijer
>            Priority: Critical
>             Fix For: 2.0.15
>
>         Attachments: conditional_insert_failure_cleaned.txt
>
>
> Cassandra claims CAS precondition didn't match current values[1], but the row is still inserted.
> We are having a quite simple cf schema:
> {code:xml}
> create table index (
>   u text PRIMARY KEY,
>   abc set<uuid>,
> ) WITH
>   compaction={'class': 'LeveledCompactionStrategy'};
> {code}
> CQL statement:
> {code:xml}
> INSERT INTO index(u, abc) VALUES(?, ?) IF NOT EXISTS
> {code}
> Sometimes, especially during some write load, Cassandra claims the conditional insert wasn't satisfied ([applied] false), but the row is still inserted.
> The response from the conditional insert contains [applied]=false + the data we tried to insert.
> A full CQL trace is attached.
> [1] CAS precondition      CAS precondition org.apache.cassandra.cql3.statements.CQL3CasConditions@1b2576ce does not match current values ColumnFamily(username_index -{deletedAt=-9223372036854775808, localDeletion=2147483647, ranges=[abc-abc:!, deletedAt=1427889576525999, localDeletion=1427889564]}- [:false:0@1427889576526000,abc:39f1a470ee694761a8197c0d0ada8e8f:false:0@1427889576526000,]) | 11:59:37.060 | /10.0.0.1 | 533702



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)