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

resharding_test_fixture doesn't configure failpoints for all nodes of config server

    • Fully Compatible
    • ALL
    • v6.0, v5.0
    • Sharding 2022-08-08
    • 55
    • 3

      The resharding_test_fixture.js configures multiple failpoints including "reshardingPauseCoordinatorBeforeCompletion" during setup only on the primary in the initial topology state. resharding_nonblocking_coordinator_rebuild.js is one test which enables elections which also enable them for config server in addition to shard replica sets. 

      It is possible for the config server to have a change in primary during the execution of test and the new server won't have the failpoints configured causing the ReshardingCoordinator to return without blocking. Any tests dependent on the behavior of the reshardingPauseCoordinatorBeforeCompletion failpoint configured by the ReshardingTest fixture can potentially surface this issue.

            abdul.qadeer@mongodb.com Abdul Qadeer
            abdul.qadeer@mongodb.com Abdul Qadeer
            0 Vote for this issue
            3 Start watching this issue