cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-1451) Shutting down a node "cleanly" still kills client requests when the node goes down
Date Sun, 15 May 2011 14:27:47 GMT

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

Jonathan Ellis commented on CASSANDRA-1451:
-------------------------------------------

Instead of trying to make this an integrated part of drain, if we had a manually "shut down
gossip" jmx control, we could have a simple workflow of

1) shut down gossip
2) wait for everyone to mark node-to-drain as down
3) drain

with no further changes required to internals, and no new exception types to introduce.

> Shutting down a node "cleanly" still kills client requests when the node goes down
> ----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1451
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1451
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: David King
>            Priority: Minor
>             Fix For: 1.0
>
>
> Shutting down a node, even more cleanly through drain, still kills some requests with
timeoutexceptions. Ideally, operations would not be sent at all to nodes that are known to
be shutting down, perhaps by shutting down gossip before starting the draining process. 
> Other nodes will still need to have the phi convict threshold exceeded, but presumably
that's usually shorter than drain

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message