[
https://issues.apache.org/jira/browse/CASSANDRA-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350639#comment-14350639
]
Brandon Williams commented on CASSANDRA-8236:
---------------------------------------------
bq. I think originally you wanted to do this for RPC_READY too but then settled
for a new ApplicationState flag. Why?
That was the only way I could see around the gossip settling period so it could
broadcast to nodes that it was done, as Tyler suggested in the description.
bq. One more thing, this patch only delays "node added", not "node up", I
assume you are aware of this and it is OK.
I honestly don't know if it's ok, because I know nothing about how clients work
anymore. That's just not my kung fu, so hopefully it can be yours? :) I know
gossip, though, and I kind of don't like burning a state just for moving,
especially since that's obsoleted by vnodes, and we can never undo an
ApplicationState.
> Delay "node up" and "node added" notifications until native protocol server
> is started
> --------------------------------------------------------------------------------------
>
> Key: CASSANDRA-8236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8236
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Tyler Hobbs
> Assignee: Brandon Williams
> Fix For: 3.0
>
> Attachments: 8236.txt
>
>
> As discussed in CASSANDRA-7510, there is still a gap between when a "node up"
> or "node added" notification may be sent to native protocol clients (in
> response to a gossip event) and when the native protocol server is ready to
> serve requests.
> Everything in between the call to {{StorageService.instance.initServer()}}
> and creation of the native server in {{CassandraDaemon.setup()}} contributes
> to this delay, but waiting for Gossip to settle introduces the biggest delay.
> We may need to introduce a "STARTING" gossip state for the period inbetween,
> which is why this is scheduled for 3.0. If there's a better option, though,
> it may make sense to put this in 2.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
