Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-53886

[BP 6.6.6] Node is not upgraded and stuck trying to register with CC

    XMLWordPrintable

Details

    • Untriaged
    • 1
    • Yes
    • Analytics Sprint 5

    Description

      During upgrading nodes, a node could get into a state where the monitor for the cluster compatibility is not started because the coordinator on the node is not started. If the monitor for the cluster compatibility is not started, the node won't detect that the cluster compatibility has changed and act on it.

      The attached logs show that the node could not finish booting and registering with the CC as it was still running an older version than the CC, and therefore, the coordinator was not started.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              ali.alsuliman Ali Alsuliman
              ali.alsuliman Ali Alsuliman
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty