[SERVER-29256] DatabaseCloner fails to parse CollectionOptions if listCollections returns metadata with UUIDs Created: 17/May/17  Updated: 30/Oct/23  Resolved: 17/May/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.5.8

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-27987 Store collection UUIDs in the databas... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2017-05-29
Participants:

 Description   

If we attempt to start up a replica set with more than one node and enable collection UUIDs (--setParameter=enableCollectionUUIDs=true), the initial sync will fail because of the new UUIDs included in the collection metadata returned by listCollections. This is because DatabaseCloner is using a mode of CollectionOptions::parse() that is more suited to validating CollectionOptions provided by the user at collection creation time, not an existing CollectionOptions with a generated UUID.



 Comments   
Comment by Githook User [ 17/May/17 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-29256 DatabaseCloner accepts CollectionOptions with UUID
Branch: master
https://github.com/mongodb/mongo/commit/f4c3c8d6e2874dc52cf4cee262d3839377651fc3

Generated at Thu Feb 08 04:20:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.