You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Ryan McGuire (JIRA)" <ji...@apache.org> on 2014/04/30 02:51:16 UTC

[jira] [Updated] (CASSANDRA-6943) UpdateFunction.abortEarly can cause BTree.update to leave its Builder in a bad state, which affects future operations

     [ https://issues.apache.org/jira/browse/CASSANDRA-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McGuire updated CASSANDRA-6943:
------------------------------------

    Labels: qa-resolved  (was: )

> UpdateFunction.abortEarly can cause BTree.update to leave its Builder in a bad state, which affects future operations
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6943
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6943
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Russ Hatch
>            Assignee: Benedict
>              Labels: qa-resolved
>             Fix For: 2.1 beta2
>
>         Attachments: 6943.2.txt, 6943.txt, node4.log, node4_jstack.log, node5.log, node5_jstack.log, node6.log, node6_jstack.log, node7.log, node7_jstack.log, screenshot.png, screenshot2.png, stress_jstack.log
>
>
> Running performance scenarios I have seen this characteristic drop in performance happen several times. A similar effect was reproduced in another test cluster. Operations eventually come to a standstill.
> !screenshot.png!
> !screenshot2.png!



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