Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-68670

Cache imbalanced collections for balancing

    • Fully Compatible
    • ALL
    • v6.3, v6.0
    • Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03
    • 161

      At the beginning of every balancing round, data size stats are collected from each shards in order to spot potential imbalance and schedule migrations. Currently, the balancer is requesting such stats in batches, collecting info for up to 20 collections per request.

      Purpose of this ticket is to rethink the current batching policy because this hardcoded limit may become source of scalability issues in case of thousands of sharded collections.

      [EDIT] REPURPOSED: this ticket also added a cache of imbalanced collections that lives between rounds in order to remember which collections had a migration scheduled during the previous round.

            silvia.surroca@mongodb.com Silvia Surroca
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            0 Vote for this issue
            6 Start watching this issue