Hi Durai, Rebalancing will only happen when the forest configuration changes. So you start off with two forests, inserts are spread according to the assignment policy. Then you add another forest (on a different, new node in the cluster for instance), and buckets are re-arranged across the forests, and rebalancing kicks in to move over the relocated buckets to their new forests. It is not (directly) related to ingest or removal of documents.
There is no need to turn off rebalancing once it has settled down, and you are not planning forest changes. I would also recommend against that, unless you have a clear reason to temporarily want to interrupt that.. Kind regards, Geert From: <[email protected]<mailto:[email protected]>> on behalf of Pavadaidurai A <[email protected]<mailto:[email protected]>> Reply-To: MarkLogic Developer Discussion <[email protected]<mailto:[email protected]>> Date: Monday, February 1, 2016 at 6:02 AM To: MarkLogic Developer Discussion <[email protected]<mailto:[email protected]>> Subject: [MarkLogic Dev General] Rebalancer Dear all, I have disabled the rebalance as shown below, since the rebalancing is resource consuming and slows down the application. With the below configuration, will the new inserts into the database use bucket assignment policy? Or should the rebalance be enabled even for the new inserts? rebalancer enable true false Enable automatic rebalancing after configuration changes. rebalancer throttle Larger numbers mean work harder at rebalancing. ________________________________ assignment policy What policy to use for assignment and rebalancing. Thanks, Durai.
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
