[
https://issues.apache.org/jira/browse/CASSANDRA-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934831#action_12934831
]
Gary Dusbabek commented on CASSANDRA-1451:
------------------------------------------
An approach:
More cleanly: introduce a gossip state in conjunction with
ApplicationState.STATUS that basically proclaims "I'm up, but stop routing
requests to me." (e.g.: see StorageService.startLeaving()). But then you'd be
at the mercy of relying on when that information makes it to every node. We
might already have a such a state, but it doesn't imply these semantics.
Even more cleanly: When a node is in that state and it receives a request from
another node that doesn't know it, have send a message that politely explains
the situation and "please stop sending me requests." Ideally, this would be
done by forcing a gossip to the node that doesn't know the leaving node doesn't
want requests (as opposed to creating a new message, verb handler, etc.).
> 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.
