Hello Isaac,
While the collector rebalancing does not occur on an interval, there are certain situations outside of a manual run where a rebalance is triggered. This is explained further in the KB article When a Collector Load Balancing is triggered, and what impact can that have? (sciencelogic.com).
From the article, the following can trigger a rebalance:
- A new device is created: the balancer assigns the device to a collector in the device's CUG.
- A collector fails over and enters the failed over state: the balancer assigns the failed over collector's devices to available collectors (provided the maximum allowed collector outage has not been reached).
- A collector fails back from the failed over state: the balancer rebalances the CUG by reassigning all devices to available collectors.
- The user adds or removes a collector using the UI's CUG administration page (admin_collector_groups): the balancer rebalances the CUG by reassigning all devices to available collectors (provided the maximum allowed collector outage has not been reached).
- The user clicks a CUG's lightning bolt in the UI's CUG administration page: the balancer reassigns all devices to the available collectors in the CUG.
- The user enables High Availability for a CUG in the UI's CUG administration page: the balancer reassigns all devices to the available collectors in the CUG.
For now, there are no plans to set the collector rebalancing on an interval.
Antonio Andres
Senior Technical Support Engineer | ScienceLogic
Expert
