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

autofailover should not auto failover anybody when rebalance is marked as in-progress. Or at least be more careful there

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 1.8.1
    • 1.8.0
    • ns_server
    • Security Level: Public

    Description

      In one of customers:

      • rebalance was running
      • node orchestrating rebalance failed
      • node orchestrating rebalance was automatically failed over by new master
      • node orchestrating rebalance re-joined (still thinking it was rebalancing see MB-5049)
      • we had config conflict and bad things as a result

      Looks like during rebalance we should just disable autofailover because during rebalance humans can take care of correct actions

      Attachments

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

        Activity

          People

            alkondratenko Aleksey Kondratenko (Inactive)
            alkondratenko Aleksey Kondratenko (Inactive)
            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