Operational Defect Database
BugZero found this defect 62 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2611744
Collection sharded with a hashed key not pre-split correctly
Last update date:
3/18/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
In a two-shard cluster, an empty collection sharded with a hashed key should create two chunks and each shard should own one chunk. When there is a concurrent setFCV operation, the two chunks could both live on only one of the shards. This could be due to shardCollection checking the value of an unstable featureFlag twice during its execution. It is mentioned during discussion that gOneChunkPerShardEmptyCollectionWithHashedShardKey feature flag is data-racy in presence of an FCV downgrade.
Top User Comments
Steps to Reproduce
