You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2013/10/28 18:54:39 UTC

[jira] [Commented] (CASSANDRA-6244) calculatePendingRanges could be asynchronous on 1.2 too

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

Brandon Williams commented on CASSANDRA-6244:
---------------------------------------------

Thanks for the backport [~rwfowler].  Can you provide some evidence of this being a problem?  I ask because in 1.2 CASSANDRA-3881 _should_ make this fast enough to not be an issue, which is why we didn't put CASSANDRA-5135 in the 1.2 branch.

> calculatePendingRanges could be asynchronous on 1.2 too
> -------------------------------------------------------
>
>                 Key: CASSANDRA-6244
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6244
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: Cassandra 1.2, AWS
>            Reporter: Ryan Fowler
>             Fix For: 1.2.12
>
>         Attachments: 6244.txt
>
>
> calculatePendingRanges can hang up the Gossip thread to the point of a node marking all the other nodes down.
> I noticed that the same problem was resolved with CASSANDRA-5135, so I attempted to port the patch from that issue to the 1.2 codebase.



--
This message was sent by Atlassian JIRA
(v6.1#6144)