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

Rename 3.2 failApplyChunkOps and 3.4 failCommitMigrationCommand failpoints to coincide

XMLWordPrintableJSON

    • 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_failure.js is currently blacklisted from the new sharding_last_stable_mongos_and_mixed_shards suite because it exercises a failpoint that doesn't exist in 3.2 and thus doesn't work with 3.2 shards.

      3.2 failApplyChunkOps behaves in the same way as 3.4 failCommitMigrationCommand failpoint, but just in different code paths because of changes made to 3.4. Rename both or one and get the JS test off the suite's blacklist.

            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: