[SERVER-51056] Disable refine_collection_shard_key_atomic.js from running in sharding_csrs_continuous_config_stepdown suite Created: 18/Sep/20 Updated: 29/Oct/23 Resolved: 01/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.8.0, 4.4.16 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Sergi Mateo Bellido |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.4
|
||||||||
| Sprint: | Sharding 2020-10-05 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 15 | ||||||||
| Description |
|
Similar to other tests who set a failpoint on the config server primary, refine_collection_shard_key_atomic.js should not run in the sharding_csrs_continuous_config_stepdown suite refine_collection_shard_key_atomic.js sets the failpoint hangRefineCollectionShardKeyBeforeCommit on the config server primary. If the config server primary steps down, and a new primary steps up and successfully refines the shard key, the failpoint will never get hit. |
| Comments |
| Comment by Githook User [ 22/Jul/22 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: (cherry picked from commit c1401d158b915996aacd0e43b666ca3f7b0e9305) |
| Comment by Githook User [ 01/Oct/20 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |