Details
-
New Feature
-
Resolution: Done
-
Major
-
None
-
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
-
K8S-3354 Cloud Native 2.6.1 - Release Notes
- Closed