You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/04/12 00:23:05 UTC

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

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

Jonathan Ellis updated CASSANDRA-1451:
--------------------------------------

             Priority: Minor  (was: Major)
    Affects Version/s:     (was: 0.6.5)
        Fix Version/s: 1.0
           Issue Type: New Feature  (was: Bug)

> 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