Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-8236

Delay "node up" and "node added" notifications until native protocol server is started

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 2.2.0 beta 1
    • Component/s: Legacy/CQL
    • Labels:
      None

      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.

        Attachments

        1. 8236.txt
          5 kB
          Brandon Williams

          Issue Links

            Activity

              People

              • Assignee:
                stefania Stefania Alborghetti
                Reporter:
                thobbs Tom Hobbs
                Authors:
                Stefania Alborghetti
                Reviewers:
                Brandon Williams
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: