[SERVER-56659] Use local write concern when acquiring and releasing resumable critical section in resharding recipient Created: 05/May/21  Updated: 29/Oct/23  Resolved: 19/May/21

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

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: PM-234-M3, PM-234-T-lifecycle, post-rc0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-53653 [Resharding] Take the critical sectio... Closed
depends on SERVER-55511 Handle recovery for resharding recipi... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Sharding 2021-05-31
Participants:
Story Points: 1

 Description   

The changes from 70d2f7f as part of SERVER-53653 use ShardingCatalogClient::kMajorityWriteConcern in a couple places:

  1. As part of releasing the critical section on abort.
  2. As part of acquiring the critical section before transition to kStrictConsistency.

After the changes from SERVER-55511, it'll be possible to rely on the recovery process in the RecipientStateMachine to correctly reacquire the critical section if the local write hadn't become majority-committed following the failover. The ShardingCatalogClient::kMajorityWriteConcern can then safely be changed to ShardingCatalogClient::kLocalWriteConcern.

Note that we can consolidate releasing the critical section in RecipientStateMachine::_finishReshardingOperation() similar to what is being done in DonorStateMachine::_finishReshardingOperation().



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 19/May/21 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-56659 Use local write concern when acquiring and releasing resumable critical section in resharding recipient

(cherry picked from commit d9a38007836d30a03407bfcc3d790d26091a9868)
Branch: v5.0
https://github.com/mongodb/mongo/commit/2579051eb0849791275b2c529f1ad0f11b77850b

Comment by Githook User [ 19/May/21 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-56659 Use local write concern when acquiring and releasing resumable critical section in resharding recipient
Branch: master
https://github.com/mongodb/mongo/commit/d9a38007836d30a03407bfcc3d790d26091a9868

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