Operational Defect Database
BugZero found this defect 65 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2610228
Direct connection insert race with catalog refresh in drop_collection_if_uuid_not_matching.js
Last update date:
3/15/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
SERVER-80135 make shards refresh asynchronously the collection metadata after a shardCollection. In drop_collection_if_uuid_not_matching.js a direct connection to the shard is established and after a shardCollection an insert command is executed, which races with the refresh. If the insert wins, then the test will fail with a StaleConfig error. We could fix this by making the test to wait for the refresh to happen, or force a refresh after the shardCollection.
Top User Comments
Steps to Reproduce
1. Apply attached patch 2. Run python buildscripts/resmoke.py run --suites=sharding jstests/sharding/drop_collection_if_uuid_not_matching.js --log=file --runAllFeatureFlagTests
