cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1108) ability to forcibly mark machines failed
Date Thu, 23 Dec 2010 06:17:04 GMT

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

Brandon Williams commented on CASSANDRA-1108:
---------------------------------------------

Probably, but I think the true problem here is that gossip is independent of any other operation.
  We can tank ourselves on GC for instance, but gossip still works 'well enough' to let the
node be counted as live.  Ultimately, we need a way for a 'sick' node to get marked down faster,
but in the meantime at least making it operator-controlled makes sense.

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


Mime
View raw message