[
https://issues.apache.org/jira/browse/CASSANDRA-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055972#comment-14055972
]
Sylvain Lebresne commented on CASSANDRA-7510:
---------------------------------------------
[~brandon.williams] do you have an idea of where would be a best place for
moving the current notifications so we get closer to "fired when the node is
ready to receive native protocol requests"? Regarding bootstrap, I suspect it
shouldn't be too hard to make it fired after the bootstrap rather than before
it but I'm not entirely sure where exactly we would need to put that. But if we
want to really fire the events when the native protocol server is ready, as I
said above, I suspect we might a new "I'm ready" gossip message or something
like that. Or do we?
> Notify clients that bootstrap is finished over binary protocol
> --------------------------------------------------------------
>
> Key: CASSANDRA-7510
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7510
> Project: Cassandra
> Issue Type: Bug
> Reporter: Joost Reuzel
> Priority: Minor
> Fix For: 2.0.10
>
>
> Currently, Cassandra will notify clients when a new node is added to a
> cluster. However, that node is typically not usable yet. It first needs to
> gossip its key range and finish loading all its assigned data before it
> allows clients to connect. Depending on the amount of data this may take
> quite a while. The clients in the mean time have no clue about the bootstrap
> status of that node. The only thing they can do is periodically check if it
> will accept a connection.
> My proposal would be to send an additional UP event when the bootstrap is
> done, this allows clients to mark the node initially as down/unavailable and
> simply wait for the UP event to arrive.
> Kind regards,
> Joost
--
This message was sent by Atlassian JIRA
(v6.2#6252)
