[
https://issues.apache.org/jira/browse/CASSANDRA-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934645#action_12934645
]
Matthew F. Dennis commented on CASSANDRA-1451:
----------------------------------------------
I think this would be pretty straightforward after CASSANDRA-1108 is
implemented. A node could "manually" mark it self down before starting a drain
and clear the mark, but not startup gossip again after it was drained. If it
crashed in the middle of a drain, an admin would need to manually clear the
mark.
> 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.
-
You can reply to this email to add a comment to the issue online.
