[SERVER-33150] Race between creating a system.profile collection and assigning UUIDs to non-replicated collections on clean startup Created: 06/Feb/18  Updated: 29/Oct/23  Resolved: 07/Mar/18

Status: Closed
Project: Core Server
Component/s: Upgrade/Downgrade
Affects Version/s: 3.6.2
Fix Version/s: 3.6.4

Type: Bug Priority: Major - P3
Reporter: Maria van Keulen Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage 2018-02-12, Storage NYC 2018-03-12
Participants:
Linked BF Score: 0

 Description   

If a system.profile collection is created on v3.6 after UUIDs are assigned to all non-replicated collections and before setting the featureCompatibilityVersion parameter to 3.6, this system.profile collection will not receive a UUID. This can occur on clean startup of a replica set, when the featureCompatibilityVersion must be set to 3.6 during ReplicationCoordinatorExternalStateImpl::initializeReplSetStorage.



 Comments   
Comment by Githook User [ 07/Mar/18 ]

Author:

{'email': 'xiangyu.yao@mongodb.com', 'name': 'Xiangyu Yao', 'username': 'xy24'}

Message: SERVER-33150 Prohibit enabling profiling when the FCV is uninitialized
Branch: v3.6
https://github.com/mongodb/mongo/commit/e327643809f404a856340868a8815fd7696b63cf

Comment by Xiangyu Yao (Inactive) [ 16/Feb/18 ]

I think we should probably prohibit creating the system.profile collection when FCV is Version::kUnsetDefault34Behavior

Comment by Eric Milkie [ 09/Feb/18 ]

Note that this work will be committed directly to the 3.6 branch and not to master, as the issue only applies to that branch.

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