[jira] Commented: (CASSANDRA-1451) Shutting down a node "cleanly" still kills client requests when the node goes down

["Matthew F. Dennis (JIRA)" <ji...@apache.org>]

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

Matthew F. Dennis commented on CASSANDRA-1451:
----------------------------------------------

now that CASSANDRA-1108 is in place, it seems like whenever we start draining we:

1) shutdown gossiper. This will prevent future messages from other nodes (once it propagates)
2) immediately reply to any request with a TException("node shutting down"). This will allow clients to distinguish between node is busy and node is not playing right now.  This will also allow other nodes to continue instead of waiting for RPCTimeout.

thoughts?

> 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: Bug
>          Components: Core
>    Affects Versions: 0.6.5
>            Reporter: David King
>
> 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