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

Exclude migration_coordinator_shutdown_in_critical_section.js test from the config stepdown suite

    • Fully Compatible
    • v5.1, v5.0, v4.4
    • Sharding 2021-11-01
    • 142

      The migration_coordinator_shutdown_in_critical_section.js test expects a chunk migration to still complete in the absence of a primary on the donor shard after the _configsvrCommitChunkMigration command has been successfully run on the config server primary. A newly-elected config server primary will attempt to contact a primary on the donor shard and time out waiting at around the same interval the JavaScript stepdown thread causes a new config server primary to be elected. The periodicity with the JavaScript stepdown thread prevents the moveChunk command from ever returning successfully and so the migration_coordinator_shutdown_in_critical_section.js test should be tagged with does_not_support_stepdowns.

            max.hirschhorn@mongodb.com Max Hirschhorn
            max.hirschhorn@mongodb.com Max Hirschhorn
            0 Vote for this issue
            2 Start watching this issue