Operational Defect Database
BugZero found this defect 129 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2543310
MigrationSourceManager may fail to emit the migrateChunkToNewShard due to stale ChunkManager info
Last update date:
3/15/2024
Affected products:
MongoDB Server
Affected releases:
5.3.0
3.6.0
4.0.0
4.2.0
4.4.0
5.0.0
5.2.0
5.1.0
6.0.0
6.1.0
6.2.0-rc0
6.3.0
Fixed releases:
No fixed releases provided.
Description:
Info
The scenario may be reproduced through the following sequence: 1. A migration with "nss: collName, from: shardId1, to: shardId2" starts; the MigrationSourceManager gets instantiated on shardId1, and placement information gets retrieved; at the time of the retrieval, shardId2 owns 1 collection chunk 2. A concurrent migration with "nss: collName, from: shardId2, to: anotherShardId" gets concurrently committed; shardId2 loses its last chunk (and the related op entry gets emitted) 3. The migration started on step 1 is resumed; since shardId2 reacquires its first collection chunk, a migrateChunkToNewShard should be emitted - but the placement information is stale at the time it gets evaluated
Top User Comments
Steps to Reproduce
