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

[windows] Rebalancing out the last node causes the cluster to be reinitialized

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Major
    • 2.0.1
    • 2.0.1
    • ns_server
    • Security Level: Public
    • 2.0.1-179-rel

    Description

      Steps to reproduce:

      1. Create default bucket on single node. No data.
      2. Rebalance in one more node.
      3. Delete the bucket.
      4. Rebalance out the node added in 2.
      5. After rebalance is finished, the initial node returns to the setup screen.

      Tried the same scenario on linux. After 3 is finished. the initial node remains intact.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. MB-7658 [Windows] severe timeouts in windows cluster with 2 buckets and 1 ddoc per bucket causes rebalance and other failures

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MB-7902 [windows] Rebalance exited with reason {detected_nodes_change, {ns_node_disco_events,

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              trond Trond Norbye
              deepkaran.salooja Deepkaran Salooja
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty