[SERVER-63285] Ensure CollectionUUIDMismatch error from write commands does not omit the actual collection even if unsharded Created: 04/Feb/22  Updated: 29/Oct/23  Resolved: 18/Feb/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes SERVER-79049 Server returns unexpected CollectionU... Open
Related
is related to SERVER-64872 Aggregate with collectionUUID on shar... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-02-21, Execution Team 2022-03-07
Participants:

 Description   

Say coll1 (with uuid1) is sharded and coll2 (with uuid2) is unsharded, and the command {insert: coll1, documents: [{_id: 1}], collectionUUID: uuid2} is issued where the document {_id: 1} belongs on the non-primary shard. Then the returned CollectionUUIDMismatch will erroneously not contain coll2, because it only exists on the primary shard. We should make sure that regardless of which shards are targeted and no matter whether collections are sharded are unsharded, the CollectionUUIDMismatch contains all of the information that it should.



 Comments   
Comment by Githook User [ 18/Feb/22 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-63285 Ensure `CollectionUUIDMismatch` error from write commands does not omit the actual collection even if unsharded
Branch: master
https://github.com/mongodb/mongo/commit/60cfbfffec9c659ceb98ed4ef2b9207408e4d648

Generated at Thu Feb 08 05:57:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.