Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 27 Nov 2013 17:39:49 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12681470.1385515794219.39487.1385573989613@arcas>
In-Reply-To: <JIRA.12681470.1385515794219@arcas>
References: <JIRA.12681470.1385515794219@arcas>
Subject: [jira] [Updated] (CASSANDRA-6409) gossip performance improvement at
 node startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis updated CASSANDRA-6409:
--------------------------------------

    Tester: Quentin Conner

> gossip performance improvement at node startup
> ----------------------------------------------
>
>                 Key: CASSANDRA-6409
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6409
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Quentin Conner
>            Assignee: Jonathan Ellis
>             Fix For: 1.2.13, 2.0.4
>
>         Attachments: 2013-11-26_17-40-08.png, endpointToTokenMapCPU.txt
>
>
> With large clusters (> 500 nodes) and num_tokens > 255 we sometimes see a node have trouble starting up.  CPU usage for one thread is pegged.
> We see this concurrent with Gossip flaps on the node trying to learn the ring topology.  Other nodes on the ring, that are already at steady state do not seem to suffer.  It is the node joining the large ring that has trouble.


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