[SERVER-85925] slow setFCV upgrade operation may write database profiling data to non-admin database Created: 30/Jan/24  Updated: 01/Feb/24  Resolved: 01/Feb/24

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

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:
Backports
Depends
Related
is related to SERVER-85924 Remove profiling tests from fcv upgra... Closed
is related to SERVER-72229 Implement FCV upgrade step to remove ... Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.3
Sprint: Execution Team 2024-02-05
Participants:
Linked BF Score: 5

 Description   

The setFCV commands runs collMod on the every namespace during the upgrade procedure. The collMod operation has a side effect where the global CurOp profiling level and namespace is set to the most recent namespace and the highest profiling level observed. For slow setFCV operations, this somtimes results in slow operations being logged in the system.profile collection of the last database we ran collMod on (very likely non-admin).



 Comments   
Comment by Githook User [ 31/Jan/24 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@users.noreply.github.com', 'username': 'benety'}

Message: SERVER-85925 run collMod using nested CurOp during FCV upgrade (#18556)

GitOrigin-RevId: beec06b6371b1e30acca9886aecd70a379095a65
Branch: master
https://github.com/mongodb/mongo/commit/5352e2091d4e5a9a6cc788e1444c2a2583989769

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