cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6893) Unintended update with conditional statement
Date Wed, 02 Apr 2014 16:57:17 GMT

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

Aleksey Yeschenko commented on CASSANDRA-6893:
----------------------------------------------

All right, after switching castorture to use prepared statements was able to repro immediately
with default params (w/ 30% of acknowledged writes lost). The attached patch fixes the issue.
Reviewing now.

> Unintended update with conditional statement
> --------------------------------------------
>
>                 Key: CASSANDRA-6893
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6893
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Ubuntu Precise 64bit / Cassandra 2.0.6
>            Reporter: Suguru Namura
>            Assignee: Sylvain Lebresne
>             Fix For: 2.0.7
>
>         Attachments: 6893.txt, ConcurrentCASUpdate.java
>
>
> After updated to 2.0.6, I have encountered the strange behavior of conditional updates.
> When I executed CQL like UPDATE test SET value = ? WHERE id = ? IF value = ? in concurrent,
sometimes cassandra returns true even if value is not satisfied the condition.
> I have attached the program which reproduce this issue. The program works fine in cassandra
2.0.5. But it seems that resets values while execution in 2.0.6.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message