[SERVER-67342] Tenant migration oplog buffer should be started by holding the RSTL lock Created: 16/Jun/22  Updated: 29/Oct/23  Resolved: 17/Jun/22

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

Type: Bug Priority: Major - P3
Reporter: Suganthi Mani Assignee: Suganthi Mani
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-65300 Refactor tenant migration recipient s... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Server Serverless 2022-06-27
Participants:
Linked BF Score: 151

 Description   

SERVER-65300 accidentally removed this piece of code. Though the reason they added initially is due to SERVER-54191 but that fassert mentioned in SERVER-54191 has been changed to uassert. But looking closer into the oplog buffer code, it seems it's illegal to start the replicated oplog buffer collection when the node is no longer primary, otherwise we would end up hitting other fassert and non-retryable error code like mentioned in BFs.



 Comments   
Comment by Githook User [ 17/Jun/22 ]

Author:

{'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}

Message: SERVER-67342 Tenant migration oplog buffer should be started by holding the RSTL.
Branch: master
https://github.com/mongodb/mongo/commit/1bab7ccc04b3329ab4fc1d5d498983529df0baab

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