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 2010/01/21 20:46:54 UTC

[jira] Updated: (CASSANDRA-695) Gossiper convicts same node over and over.

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

Jonathan Ellis updated CASSANDRA-695:
-------------------------------------

        Fix Version/s: 0.6
             Priority: Trivial  (was: Minor)
    Affects Version/s:     (was: 0.5)

> Gossiper convicts same node over and over.
> ------------------------------------------
>
>                 Key: CASSANDRA-695
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-695
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Gary Dusbabek
>            Assignee: Jaakko Laine
>            Priority: Trivial
>             Fix For: 0.6
>
>
> I can reproduce this in trunk or 0.5.  It is quite easy to see with logging set to DEBUG.
> 1.  Bring up several nodes.
> 2.  Kill one of them.
> Gossip still continues to examine the failed node because it is in the ring, but gets convicted over and over at every check (see FailureDetector.interpret).  If this is expected, we should consider lowering the debug statement in MessagingService.convict to TRACE.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.