[SERVER-67227] Insert with collectionUUID could implicitly create a collection if command failed with collectionUUIDMismatch Created: 13/Jun/22  Updated: 29/Oct/23  Resolved: 22/Jun/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.1, 6.1.0-rc0

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

Issue Links:
Backports
Depends
Problem/Incident
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0
Sprint: Execution Team 2022-06-27
Participants:

 Description   

This is not ideal because one large use case of using collectionUUID is that user might not know the actual collection name and relies on retrying CollectionUUIDMismatch error to tell the actual collection name, but having to deal with this side effect doesn't seem like a good user experience.

 

See the full slack discussion here.



 Comments   
Comment by Githook User [ 25/Jul/22 ]

Author:

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

Message: SERVER-67227 Avoid implicit collection creation for `collectionUUID` with insert/update commands

(cherry picked from commit 41994ed8c080afb448b20c631a66bf782a9834c0)
Branch: v6.0
https://github.com/mongodb/mongo/commit/2765c93e1aa265b19055d6b64e611ec945be3507

Comment by Githook User [ 23/Jun/22 ]

Author:

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

Message: SERVER-67227 Avoid implicit collection creation for `collectionUUID` with insert/update commands
Branch: davish/SERVER-63099
https://github.com/mongodb/mongo/commit/41994ed8c080afb448b20c631a66bf782a9834c0

Comment by Githook User [ 22/Jun/22 ]

Author:

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

Message: SERVER-67227 Avoid implicit collection creation for `collectionUUID` with insert/update commands
Branch: master
https://github.com/mongodb/mongo/commit/41994ed8c080afb448b20c631a66bf782a9834c0

Comment by Wenbin Zhu [ 17/Jun/22 ]

It turns out we don't have a perfect workaround for this in C2C, we only have a partial workaround that will not work if user renames or drops the capped collection in source cluster. So we are hoping to get this fix sooner if possible. Thanks!

Comment by Gregory Noma [ 13/Jun/22 ]

I think we can fix this by moving the collection UUID check into acquireCollection.

Generated at Thu Feb 08 06:07:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.