[SERVER-25208] Rename 3.2 failApplyChunkOps and 3.4 failCommitMigrationCommand failpoints to coincide Created: 22/Jul/16  Updated: 05/Apr/17  Resolved: 28/Oct/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done after SERVER-25207 Use failApplyChunkOps failpoint in a ... Closed
Related
is related to SERVER-26828 unblacklist tests in the sharding_las... Closed
is related to SERVER-25153 Add mixed version shards to sharding_... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2016-11-21
Participants:

 Description   

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.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 28/Oct/16 ]

About to release 3.4, and then these failpoint name incompatibilities between 3.2 and 3.4 will no longer be an issue. The tests can be unblacklisted in 3.5, when the sharding_last_stable_mongos_and_mixed_shards suite runs 3.6 and 3.4.

Generated at Thu Feb 08 04:08:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.