Operational Defect Database
BugZero found this defect 38 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2639017
Set shard marked as outstanding as recovery shard if recovery shard not yet chosen
Last update date:
4/11/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
If a transaction router receives a response without a readOnly value for an added participant, but it previously had that shard marked as readOnly, we mark the shard as "outstanding". The transaction router will treat this shard as a write shard at commit time to avoid accidentally choosing a read-optimized commit when it should not. It's possible that this shard is the only shard treated as a write shard in the commit protocol, and if so would be expected to be chosen as the recovery shard - the transaction router should pick a shard it is marking as 'outstanding' as the recovery shard if one has not yet been chosen for the transaction.
Top User Comments
Steps to Reproduce
