[ https://issues.apache.org/jira/browse/CASSANDRA-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986649#action_12986649 ]
Hudson commented on CASSANDRA-1108: ----------------------------------- Integrated in Cassandra-0.7 #208 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/208/]) Do not respond to gossip when gossip is disabled. Patch by brandonwilliams, reviewed by jbellis for CASSANDRA-1108 > ability to forcibly mark machines failed > ---------------------------------------- > > Key: CASSANDRA-1108 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1108 > Project: Cassandra > Issue Type: New Feature > Components: Tools > Reporter: Jonathan Ellis > Assignee: Brandon Williams > Priority: Minor > Fix For: 0.7.1 > > Attachments: 0002_do_not_respond_to_gossip_when_disabled-v2.txt, > 0002_do_not_respond_to_gossip_when_disabled.txt, 1108.txt > > Original Estimate: 8h > Remaining Estimate: 8h > > For when a node is failing but not yet so badly that it can't participate in > gossip (e.g. hard disk failing but not dead yet) we should give operators the > power to forcibly mark a node as dead. > I think we'd need to add an extra flag in gossip to say "this deadness is > operator-imposed" or the next heartbeat will flip it back to live. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.