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

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/11/13 00:41:17 UTC

[jira] [Updated] (CASSANDRA-6338) Make gossip tolerate slow Gossip tasks

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

Jonathan Ellis updated CASSANDRA-6338:
--------------------------------------

    Description: 
Currently if a single gossip task bogs down the gossip Stage, Gossip will mark everyone down because it hasn't seen updates from them (since they are all queued behind the slow one).

This means that full GCs can cause gossip "flapping" as well as any actually problematic tasks such as recomputing pending ranges.

  was:Currently if a single gossip task bogs down the gossip Stage, Gossip will mark everyone down because it hasn't seen updates from them (since they are all queued behind the slow one).


> Make gossip tolerate slow Gossip tasks
> --------------------------------------
>
>                 Key: CASSANDRA-6338
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6338
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>              Labels: gossip
>             Fix For: 2.0.3
>
>
> Currently if a single gossip task bogs down the gossip Stage, Gossip will mark everyone down because it hasn't seen updates from them (since they are all queued behind the slow one).
> This means that full GCs can cause gossip "flapping" as well as any actually problematic tasks such as recomputing pending ranges.



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