[ https://issues.apache.org/jira/browse/CASSANDRA-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877709#action_12877709 ] 

Jonathan Ellis commented on CASSANDRA-1108:
-------------------------------------------

re "why not shut the node down:"

the description is worded carelessly; s/failing/performing poorly/.  "performing poorly" could be the result of a number of cases where shutting down the node is suboptimal, e.g., anticompacting data for a newcomer.

> 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: Matthew F. Dennis
>            Priority: Minor
>             Fix For: 0.7
>
>
> 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.