SERVER-138544Backlog

bulkWrite on sharded cluster ignores collectionUUID on write with repeated namespace

When a {{bulkWrite}} command sent through a 9.0 mongos has two or more {{nsInfo}} entries with the same {{ns}} but different {{collectionUUID}} values, mongos merges them into one entry and forwards it to the shard. Only the first entry's {{collectionUUID}} is kept, and it is checked for every op that targets that namespace. A first entry with no {{collectionUUID}} counts too: all later UUIDs for that namespace are then dropped. As a result: * A write with a stale {{collectionUUID}} can su

Affected Versions
Versions known to exhibit this issue
8.3.139.0.4
Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue
ShardingWrite Ops
Labels
Tags and classification
qe-bf-triage-week