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

Implement random chunk selection policy for balancer for use in concurrency_*_with_balancer workloads

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.16, 4.3.1, 4.2.3, 4.0.14
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
    • Fully Compatible
    • v4.2, v4.0, v3.6
    • Sharding 2019-08-26, Sharding 2019-09-09
    • 19

      Currently, in the concurrency_*_with_balancer suites, even if the balancer is on, it may not move chunks if there is not a data imbalance across shards. This means that we are not getting as much coverage as we would like for migrations concurrent with other operations.

      To enable our concurrency tests to have better coverage of migrations during stepdowns, we would like the balancer to cause more frequent migrations. Adding a failpoint which causes the balancer to always move a random chunk (ignoring the current data distribution) will ensure that the balancer is consistently moving chunks throughout the execution of the concurrency workload.

      The alternative in the past has been to use the moveChunk command in one of the state transitions of the workload - however, moveChunk operations are currently banned for the with_stepdowns suites (which will be addressed in the future in SERVER-40713).

            alex.taskov@mongodb.com Alexander Taskov (Inactive)
            alex.taskov@mongodb.com Alexander Taskov (Inactive)
            0 Vote for this issue
            5 Start watching this issue