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 Fowler (JIRA)" <ji...@apache.org> on 2013/11/05 04:25:17 UTC
[jira] [Updated] (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:all-tabpanel ]
Ryan Fowler updated CASSANDRA-6244:
-----------------------------------
Attachment: CASSANDRA-6244-cassandra-2.0.txt
My fault. I read the log wrong. Not the first time that's happened.
Here's a patch for the cassandra-2.0 branch. The only real difference appeared to be the Table->Keyspace naming of things.
> 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
> Assignee: Ryan Fowler
> Fix For: 1.2.12
>
> Attachments: 6244.txt, CASSANDRA-6244-cassandra-2.0.txt, escalating-phi.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)