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

Stop rebalance can take a long time to take effect if we have compaction and indexing are in progress

    Details

      Description

      2 buckets (~10 M items)
      10 index building in progress
      3 compaction on views in progress

      The CPU usage here was about 80% on the orchestrator.

      It took about 10 mins for stop rebalance to take effect, from user perpective, it seems as though stop rebalance did not work.
      We could can log in UI, saying that stop rebalance is in progress, since, I believe stop rebalance is asyn call.

      Attaching the cbcollect_logs from the orchestrator.

      1. Screen Shot 2012-08-20 at 7.07.04 PM.png
        553 kB
      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        There are no open Gerrit changes for this issue.

          People

          • Assignee:
            alkondratenko Aleksey Kondratenko (Inactive)
            Reporter:
            karan Karan Kumar (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes