-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
v5.0, v4.4, v4.2
-
Execution Team 2021-10-04, Execution Team 2021-10-18, Execution Team 2022-02-07, Execution Team 2022-02-21, Execution Team 2022-03-07
-
35
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This ticket would explore whether the RSTL lock is necessary for serverStatus and collection stats.
I noticed these cmds in backtraces stuck waiting for the RSTL lock while stepdown hung. I think there are potentially valuable diagnostics we aren't for this sort of hang.
- depends on
-
SERVER-63219 Change collStats cmd to run without the RSTL lock so FTDC can continue to report during repl state changes
-
- Closed
-
- is related to
-
SERVER-64053 Support optionally skipping the RSTL lock in AutoGetOplog
-
- Closed
-
-
SERVER-63264 Create a way to have serverStatus output all sections for testing
-
- Closed
-