Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-3305

When performing swap rebalance or delta recovery upgrade, do the Orchestrator last.

    XMLWordPrintable

Details

    • New Feature
    • Resolution: Done
    • Major
    • 2.6.1
    • None
    • operator
    • Christmas and Beyond, 1 - 2024 A New Dawn
    • 3

    Description

      The orchestrator is a Couchbase Server node that is effectively the "leader" of the cluster, and if we remove the orchestrator from the cluster, before we can perform additional operations, we have to wait until a new Orchestrator is elected.

      We can find the Orchestrator info from /pools/default/terseClusterInfo which is a new endpoint that I didn't know existed.

      The gist is, we should defer the orchestrator to be the last node upgraded, as this would prevent us from going through a lengthy orchestrator election process more than once.

       

      Attachments

        Issue Links

          relates to

          Page - A new page either standalone or within a series of pages must be added K8S-3354 Cloud Native 2.6.1 - Release Notes

          • Major - Major loss of function.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              yusuf.ramzan Yusuf Ramzan
              justin.ashworth Justin Ashworth
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty