[
https://issues.apache.org/jira/browse/CASSANDRA-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803681#action_12803681
]
Hudson commented on CASSANDRA-695:
----------------------------------
Integrated in Cassandra #331 (See
[http://hudson.zones.apache.org/hudson/job/Cassandra/331/])
lower MS.convict debug statement to trace.
> 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: Gary Dusbabek
> Priority: Trivial
> Fix For: 0.6
>
> Attachments: 695.patch
>
>
> 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.
