[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:
Related
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-09-11
Participants:
Linked BF Score: 15

 Description   

It should be load()'d into both the sharding_continuous_config_stepdown.js override and the implicitly_shard_accessed_collections.js override.

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: SERVER-30675 SERVER-30678 Add configuration options to JavaScript stepdown thread
Branch: master
https://github.com/mongodb/mongo/commit/4582f2e1c51f5277488c15732374560ee8ade96f

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