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

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.0
    • Fix Version/s: 1.8.1
    • Component/s: 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

      # Subject Project Status CR V
      For Gerrit Dashboard: &For+MB-5050=message:MB-5050

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            alkondratenko Aleksey Kondratenko (Inactive)
            Reporter:
            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