Loading...

XML

Word

Printable

JSON

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.

depends on

SERVER-52770 Add abortReshardCollection command for users to cancel the resharding operation

SERVER-53258 [Resharding] Reject writes in opObserver when disallowWritesForResharding is true

is related to

SERVER-53922 Add reshardingCriticalSectionTimeoutMillis server parameter