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

Log if Node failed over is Orchestrator

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • None
    • 5.0.0
    • ns_server
    • None

    Description

      Given that changing the Orchestrator can take some time due to Erlang's Global Name registry, Can we log in the User Visible logs when the node that is failed over was the Orchestrator? This will allow customer to know that this failover might take more time than other failovers.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MB-21206 Supportability: log message “Failed to auto-failover node X within auto-failover timeout ..."

          • 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

              james.mauss James Mauss (Inactive)
              james.mauss James Mauss (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty