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

Rename 3.2 failMigrationReceivedOutOfRangeDelete and master failMigrationReceivedOutOfRangeOperation failpoint to coincide

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2016-11-21

      migration_with_source_ops.js is currently blacklisted in the new sharding_last_stable_mongo_and_mixed_shards suite. This is because a 3.2 shard cannot set a failpoint it does not have, which the 3.4 JS test calls.

      3.4 migration_with_source_ops.js exercises two points in the code with the same failpoint, whereas in 3.2 migration_with_source_deletes.js only exercises one of those point. If the name of the failpoint were the same, the test could run, if only be 50% effective failpoint-wise with a 3.2 shard – it does nothing incorrect.

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

              Created:
              Updated:
              Resolved: