Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 5 Nov 2013 03:25:17 +0000 (UTC)
From: "Ryan Fowler (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12675897.1382738306903.20651.1383621917424@arcas>
In-Reply-To: <JIRA.12675897.1382738306903@arcas>
References: <JIRA.12675897.1382738306903@arcas>
Subject: [jira] [Updated] (CASSANDRA-6244) calculatePendingRanges could be
 asynchronous on 1.2 too
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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)