[DOCS-15772] [Server] Investigate changes in SERVER-70971: [v4.4] Backport skipping RSTL lock in serverStatus Created: 01/Dec/22  Updated: 13/Nov/23  Resolved: 02/Dec/22

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 4.4.19, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Joseph Dougherty
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-70971 [v4.4] Backport skipping RSTL lock in... Closed
Related
related to DOCS-15769 [BACKPORT] [v4.4] Have FTDC code path... Closed
Participants:
Days since reply: 1 year, 9 weeks, 5 days ago
Epic Link: DOCSP-12974

 Description   
Original Downstream Change Summary

FTDC data will now always be captured and won't block shutdown. The FTDC capture process won't be blocked if step-up or step-down occurs to nodes on a replica-set.

This is mostly of interest to TSE and Server engineers as we will have better view of the server state in certain scenarios.

Description of Linked Ticket

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 Joseph Dougherty [ 02/Dec/22 ]

jordi.olivares-provencio@mongodb.com helped me confirm that these changes do not require any additional docs. There's no update to the user experience here.

Comment by Education Bot [ 01/Dec/22 ]

Fix Version updated for upstream SERVER-70971:
4.4.19

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