Operational Defect Database
BugZero found this defect 80 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2594979
ReshardingTxnCloner unnecessarily appends $incompleteOplogHistory oplog entry when retryability history is already marked incomplete
Last update date:
3/15/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
This causes the prevOpTime chain to grow and for reloading the prevOpTime chain from disk following a primary failover to take nominally longer. In extreme cases of repeated primary failovers seen in testing on slower build variants, this can prevent the ReshardingTxnCloner from making forward progress. We can skip calling resharding::data_copy::updateSessionRecord(TransactionParticipant::kDeadEndSentinel) when TransactionParticipant::hasIncompleteHistory() == true.
Top User Comments
Steps to Reproduce
