[SERVER-30678] Move shardCollection retry logic from sharding_continuous_config_stepdown.js to its own file Created: 16/Aug/17 Updated: 30/Oct/23 Resolved: 06/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.13 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding36-passthrough-testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2017-09-11 | ||||
| Participants: | |||||
| Linked BF Score: | 15 | ||||
| Description |
|
Per further discussion, since the implicitly_shard_accessed_collections.js override is used in a case where the CSRS primary isn't expected to step down, there should be no need to retry the "shardCollection' command. |
| Comments |
| Comment by Githook User [ 30/Aug/17 ] |
|
Author: {'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}Message: |