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

Operator needs more robust way to detect outcome of graceful failover

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Blocker
    • 2.6.4
    • 2.6.4
    • operator
    • 9 - Cataclysm, 10 - Path of Vengeance
    • 4

    Description

      Currently the Operator uses the pools/default/tasks REST API to detect the outcome of graceful failover. In particular, if after a successful kick-off of graceful failover the tasks REST API reports that a rebalance with subtype gracefulFailover is "notRunning", the operation is deemed to have finished successfully.

      Unfortunately, this API is not completely reliable. In particular, if graceful-failover abruptly terminates (e.g. the orchestrator crashes) the tasks API will show that the graceful failover is not running and the Operator will incorrectly conclude that it finished successfully.

      Attachments

        Issue Links

          For Gerrit Dashboard: K8S-3472
          # Subject Branch Project Status CR V

          Activity

            People

              usamah.jassat Usamah Jassat
              dfinlay Dave Finlay
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty