Operational Defect Database
BugZero found this defect 20 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2656573
Avoid calling shard server opobserver during recovery procedures
Last update date:
4/29/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
It seems there is an issue when an initial sync node attempts to acquire collection locks on a view during oplog replay. The lock acquisition would fail with CommandNotSupportedOnView. This results in updates/deletes not being applied correctly on the initial syncing node, leading to data inconsistency. To resolve this, we should ensure that the shard server op observer does not run during recovery procedures. It looks like today we skip running the shard server op observer functions only if the node is standalone or primary.
Top User Comments
Steps to Reproduce
