[
https://issues.apache.org/jira/browse/CASSANDRA-9245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572845#comment-14572845
]
Philip Thompson commented on CASSANDRA-9245:
--------------------------------------------
[~brandon.williams], do we need to make this change?
> 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)
