[CASSANDRA-8236] Delay "node up" and "node added" notifications until native protocol server is started

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.0 beta 1
• Component/s: Legacy/CQL
• Assignee: Stefania Alborghetti
• Reporter: Tom Hobbs

Authors

Stefania Alborghetti

Reviewers

Brandon Williams

• Created: 31/Oct/14 20:46
• Updated: 16/Apr/19 09:31
• Resolved: 30/Mar/15 14:19

Description

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.

Issue Links

• is duplicated by: CASSANDRA-8450 Cassandra node announces availability before it is ready to accept CQL clients
• is related to: CASSANDRA-12781 Disable RPC_READY gossip flag when shutting down client servers
• links to: dtests
• links to: Patch