You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2011/01/25 17:15:48 UTC

[jira] Reopened: (CASSANDRA-1108) ability to forcibly mark machines failed

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

Brandon Williams reopened CASSANDRA-1108:
-----------------------------------------


Turns out this isn't good enough.  We've shutdown the Gossiper's timer on node A, but node B will call gossipToUnreachableEndpoints, choose A, and A will still reply.

> 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: 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.