[SERVER-70971] [v4.4] Backport skipping RSTL lock in serverStatus Created: 31/Oct/22  Updated: 29/Oct/23  Resolved: 01/Dec/22

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

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

Issue Links:
Depends
Documented
is documented by DOCS-15772 [Server] Investigate changes in SERVE... Closed
Problem/Incident
Related
related to SERVER-30888 Have FTDC code paths obtain locks wit... Closed
Backwards Compatibility: Minor Change
Sprint: Execution Team 2022-12-12, Execution Team 2022-11-28
Participants:
Case:

 Description   

In 5.0, 4.4, and 4.2 the serverStatus command unnecessarily acquires the RSTL lock for producing the results. This can cause issues with FTDC data reporting as it can have empty reporting periods due to waiting for the lock.

To solve this in SERVER-60016 we skip the RSTL lock acquisition. That change should be backported. It also requires backporting part of SERVER-50678 for the skipRSTLLock parameter in GlobalLock.

The backport to 5.0 is already handled by BACKPORT-13878.



 Comments   
Comment by Githook User [ 01/Dec/22 ]

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-70971 Skip RSTL lock acquisition during FTDC data capture
Branch: v4.4
https://github.com/mongodb/mongo/commit/0db1299fe80956fe134a0816e1e9d2b2149f3bc2

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