[SERVER-53882] TenantMigrationAccessBlocker::setCommitOpTime and setAbortOpTime could cause migration to transition out of blocking state before the commit or abort opTime is majority-committed Created: 19/Jan/21  Updated: 29/Oct/23  Resolved: 19/Jan/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Bug Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-A
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-01-25
Participants:

 Description   

The condition here should be

 

opTime < repl::ReplicationCoordinator::get(opCtx)>getCurrentCommittedSnapshotOpTime()

instead. 

 



 Comments   
Comment by Githook User [ 19/Jan/21 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}

Message: SERVER-53882 TenantMigrationAccessBlocker::setCommitOpTime and setAbortOpTime could cause migration to transition out of blocking state before the commit or abort opTime is majority-committed
Branch: master
https://github.com/mongodb/mongo/commit/62c3c9593faeb06f79a388cb1d3b028d37cee35f

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