http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/MB-6339 Couchbase Server 2 buckets (~10 M items) <br/> 10 index building in progress <br/> 3 compaction on views in progress <br/> <br/> The CPU usage here was about 80% on the orchestrator. <br/> <br/> It took about 10 mins for stop rebalance to take effect, from user perpective, it seems as though stop rebalance did not work. <br/> We could can log in UI, saying that stop rebalance is in progress, since, I believe stop rebalance is asyn call. <br/> <br/> Attaching the cbcollect_logs from the orchestrator. <br/> <br/> <br/> <br/> 2.0.0-1613-rel MB-6339

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

Bug Minor Closed Duplicate Public Aleksey Kondratenko Karan Kumar 2.0-beta-release-notes 2.0-release-notes Mon, 20 Aug 2012 21:14:46 -0500 Wed, 9 Jan 2013 23:13:18 -0600 Thu, 25 Oct 2012 16:23:36 -0500 2.0-beta .next documentation UI 0 1 There&#39;s even larger problem I&#39;m aware of. Sometimes it needs really long time to stop if. For example when some node is totally down. <br/> I&#39;ve added a note to the release notes as a known issue for this behaviour. Has the UI component been changed? If not, it should be reassigned for a fix. alk makes more sense than peter for assignment Fixed already. Date of First Response Mon, 20 Aug 2012 21:23:05 -0500 Rank 4251 Time In Status