You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2014/04/02 05:24:16 UTC
[jira] [Commented] (CASSANDRA-6893) Unintended update with
conditional statement
[ https://issues.apache.org/jira/browse/CASSANDRA-6893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957298#comment-13957298 ]
Aleksey Yeschenko commented on CASSANDRA-6893:
----------------------------------------------
Not able to reproduce on my macbook, neither using modified dtest not https://github.com/iamaleksey/castorture, with or without the patch, so far. Able to fail the test, but it's too conservative in its assert -
{code}
assert (value == N * I) and (errors == 0) and (gaveup == 0)
{code}
is unrealistic with high enough contention.
> 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)