[
https://issues.apache.org/jira/browse/CASSANDRA-15349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968235#comment-16968235
]
Jorge Bay commented on CASSANDRA-15349:
---------------------------------------
>From the driver side, we currently register to events only on the control
>connection because the events are relevant to the state of the cluster as a
>whole.
In this case, given that is per connection (really per host, but its usually 1
connection per host) it could make sense to receive an event directly on each
connection.
We could reuse the existing event flow, adding a new event that all driver
connections register to, something like "GOING_AWAY" that will tell the driver
to drain the connection and close it, while avoiding to send additional
requests to that node. The server node could wait for a window for all the
client connections to be closed, starting tcp termination on the remaining
connections.
> Add “Going away” message to the client protocol
> -----------------------------------------------
>
> Key: CASSANDRA-15349
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15349
> Project: Cassandra
> Issue Type: New Feature
> Components: Messaging/Client
> Reporter: Alex Petrov
> Priority: Normal
> Labels: client-impacting
>
> Add “Going away” message that allows node to announce its shutdown and let
> clients gracefully shutdown and not attempt further requests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
