[
https://issues.apache.org/jira/browse/CASSANDRA-9245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573132#comment-14573132
]
Tyler Hobbs edited comment on CASSANDRA-9245 at 6/4/15 4:58 PM:
----------------------------------------------------------------
CASSANDRA-8236 should eliminate the gap in 2.2+, but I think it would be good
to update the docs to mention that the delay will be longer in versions before
2.2.
was (Author: thobbs):
CASSANDRA-8236 should eliminate the gap in 2.2+, but I think it would be good
to update the docs to mention that the delay may be longer in versions before
2.2.
> Host up / new node event delay can be at minimum 8 seconds, protocols docs
> suggest 1 second
> -------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-9245
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9245
> Project: Cassandra
> Issue Type: Bug
> Components: Documentation & website
> Reporter: Chris Bannister
> Priority: Minor
>
> In the protocol documentation for NEW_NODE and UP events it suggests to
> connect to the node after a delay due to the event being fired once gossip
> detects the node but the node wont listen for clients until
> waitForGossipToSettle which will take a minimum of 8 seconds to complete (if
> it is not disabled).
> Thus suggesting that 1 second is enough is not correct and clients will still
> get a connect refused.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
