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

The `migration_sets_fromMigrate_flag.js` test is not compatible with sharding continuous stepdown suite

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.6.1
    • 3.4.19, 3.6.3, 3.7.1
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • v3.6, v3.4
    • Sharding 2018-01-15
    • 0

    Description

      The `migration_sets_fromMigrate_flag.js` test occasionally fails in the continuous stepdown suite because the config server balancer steps down and cases moveChunk to run one time too many, which causes more 'i' entries to be present in the recipient's oplog.

      Specifically, from the logs it can be seen that the migration, which fails due to 'failMigrationLeaveOrphans' happening twice due to the balancer recovery:

      d23264| 2017-12-18T22:20:05.678+0000 W COMMAND  [conn29] failpoint: failMigrationLeaveOrphans set to: { mode: 1, data: {} }
      ...
      d23264| 2017-12-18T22:20:08.319+0000 I SHARDING [migrateThread] failing migration after cloning 1 docs due to failMigrationLeaveOrphans failpoint
      d23261| 2017-12-18T22:20:16.026+0000 W SHARDING [conn26] Chunk move failed :: caused by :: OperationFailed: Data transfer error: failing migration after cloning 1 docs due to failMigrationLeaveOrphans failpoint
      ...
      d23264| 2017-12-18T22:20:16.210+0000 I SHARDING [migrateThread] failing migration after cloning 1 docs due to failMigrationLeaveOrphans failpoint
      

      This test should be blacklisted from the continuous stepdown suite.

      Attachments

        Activity

          People

            kaloian.manassiev@mongodb.com Kaloian Manassiev
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: