[SERVER-82838] ReshardingOplogApplier uses {w: "majority", wtimeout: 60000} write concern when persisting resharding oplog application progress Created: 06/Nov/23  Updated: 25/Jan/24  Resolved: 14/Dec/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 5.0.0, 6.0.0, 7.0.0, 7.1.0
Fix Version/s: 7.3.0-rc0, 7.0.5, 6.0.13, 5.0.24

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Wenqin Ye
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Problem/Incident
is caused by SERVER-53915 Persist total number of oplog entries... Closed
Related
is related to SERVER-61052 Resharding Donor & Recipient's Coordi... Closed
Assigned Teams:
Cluster Scalability
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.2, v7.0, v6.0, v5.0
Sprint: Cluster Scalability 2023-12-25
Participants:
Story Points: 2

 Description   

The PersistentTaskStore class called by the ReshardingOplogApplier uses WriteConcerns::kMajorityWriteConcernShardingTimeout when no argument is provided. The {w: "majority", wtimeout: 60000} write concern can lead resharding to fail with an operation-fatal error due to the write concern not being satisfied quickly enough. Furthermore, there is no requirement for the ReshardingOplogApplier to have its current batch become majority-committed before moving on to process the subsequent batch. This is because the new primary of the recipient shard will resume resharding batch application from wherever its local state left off from.

The ReshardingOplogApplier should instead use {w: 1} for its write concern (for example).



 Comments   
Comment by Githook User [ 15/Dec/23 ]

Author:

{'name': 'Wenqin Ye', 'email': 'wenqin908@gmail.com', 'username': 'wenqinYe'}

Message: SERVER-82838: Change ReshardingOplogApplier to use w:1 write concern when persisting resharding oplog application progress

GitOrigin-RevId: f85825707f14b8949e85528705b0e962b5b2ed74
Branch: v6.0
https://github.com/mongodb/mongo/commit/f98ce1cfaf81046aa1378960da5fea7ce46ddc10

Comment by Githook User [ 15/Dec/23 ]

Author:

{'name': 'Wenqin Ye', 'email': 'wenqin908@gmail.com', 'username': 'wenqinYe'}

Message: SERVER-82838: Change ReshardingOplogApplier to use w:1 write concern when persisting resharding oplog application progress

GitOrigin-RevId: e6d13d6c92a1fd86144f27b89692a86836621bfd
Branch: v5.0
https://github.com/mongodb/mongo/commit/ce67816901ba3d1c160a98e456b1a2abdfce8086

Comment by Githook User [ 15/Dec/23 ]

Author:

{'name': 'Wenqin Ye', 'email': 'wenqin908@gmail.com', 'username': 'wenqinYe'}

Message: SERVER-82838: Change ReshardingOplogApplier to use w:1 write concern when persisting resharding oplog application progress

(cherry picked from commit de25291fb15bff069f33fe11e8ed24ff5894e570)

GitOrigin-RevId: 68122c2f89c26c99ed64d91b1762248da12dec12
Branch: v7.0
https://github.com/mongodb/mongo/commit/1fa2d562251ec83228b1c95859a241687662f930

Comment by Githook User [ 14/Dec/23 ]

Author:

{'name': 'Wenqin Ye', 'email': 'wenqin908@gmail.com', 'username': 'wenqinYe'}

Message: SERVER-82838: Change ReshardingOplogApplier to use w:1 write concern when persisting resharding oplog application progress

GitOrigin-RevId: de25291fb15bff069f33fe11e8ed24ff5894e570
Branch: master
https://github.com/mongodb/mongo/commit/9a28587ab0b902ad6e3aa71bb525c61bdd0f69d9

Generated at Thu Feb 08 06:50:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.