[SERVER-53923] Enforce reshardingCriticalSectionTimeout parameter Created: 20/Jan/21  Updated: 29/Oct/23  Resolved: 31/Mar/21

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

Type: New Feature Priority: Major - P3
Reporter: Lamont Nelson Assignee: Kshitij Gupta
Resolution: Fixed Votes: 0
Labels: PM-234-M3, PM-234-T-autocommits
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-52770 Add abortReshardCollection command fo... Closed
depends on SERVER-53258 [Resharding] Reject writes in opObser... Closed
Problem/Incident
Related
is related to SERVER-53922 Add reshardingCriticalSectionTimeoutM... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-04-05
Participants:
Linked BF Score: 62
Story Points: 2

 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.
  • Should abort the resharding operation if the timeout is reached before reaching strict consistency after engaging the critical section.


 Comments   
Comment by Githook User [ 31/Mar/21 ]

Author:

{'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}

Message: SERVER-53923: Enforce reshardingCriticalSectionTimeout parameter.
Branch: master
https://github.com/mongodb/mongo/commit/5ac830813af2b84752aecc02d1dc6558274ff2fd

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