[SERVER-53922] Add reshardingCriticalSectionTimeoutMillis server parameter Created: 20/Jan/21  Updated: 06/Dec/22  Resolved: 20/Jan/21

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

Type: New Feature Priority: Major - P3
Reporter: Lamont Nelson Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: PM-234-T-autocommits
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-53923 Enforce reshardingCriticalSectionTime... Closed
Assigned Teams:
Sharding
Participants:

 Description   

Add a server parameter for an upper limit on how long to wait to hear back from recipient shards reaching strict consistency after engaging the critical section. This is to bound the amount of write unavailability in case the estimated time remaining turns out to be inaccurate. Default value isn’t decided but should be around 5-10 seconds



 Comments   
Comment by Lamont Nelson [ 20/Jan/21 ]

merged with SERVER-53923

Generated at Thu Feb 08 05:32:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.