[
https://issues.apache.org/jira/browse/CASSANDRA-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183495#comment-14183495
]
Brandon Williams commented on CASSANDRA-7510:
---------------------------------------------
Argh, gossip settling.
bq. I'm not sure that we can do anything about this without adding something
new to gossip, though.
I'm not sure we can either, and it'd be strange if we did, since we'd
essentially have two events that mean 'ready' unless we did something like
suppress the rpc_address state until it was bound, but that probably breaks
clients in some other way at this point.
> 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
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 2.0.12
>
> Attachments: 7510.txt
>
>
> 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.3.4#6332)
