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

Pull out "migrationCommitError" and "migrationCommitVersionError" failpoints and replace them with more comprehensive jstest coverage

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding 2016-09-19, Sharding 2016-10-10, Sharding 2016-10-31

    Description

      The failpoints test that the source shard of a migration behaves correctly when they receive an error response from the config server due to the failpoints. However, they do not test the CommitChunkMigration command's ability to perceive such errors, since the checks are just being arbitrarily tripped by the failpoints.

      So instead, alter the config.chunks and config.locks collections directly in the JS test, in the middle of moveChunk commands, so that the CommitChunkMigration command will catch the errors on its own without failpoints doing so for the command.

      Attachments

        Activity

          People

            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: