Operational Defect Database
BugZero found this defect 54 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2623116
ConvertToCappedCoordinator may leave dirty metadata on the sharding catalog when interrupted by multiple stepdown events
Last update date:
3/26/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
The "commit to the sharding catalog" phase of ConvertToCappedCoordinator defines a conditional multi-step clean up process of partial writes performed in a previous attempt that first removes the entry from config.collections and later deletes the related config.chunks documents. Nevertheless, if a second step-down occurs between these two steps, the next retry won't perform any cleanup at all, since the initial condition will evaluate to false.
Top User Comments
Steps to Reproduce
