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
- is related to
SERVER-64053 Support optionally skipping the RSTL lock in AutoGetOplog
SERVER-63264 Create a way to have serverStatus output all sections for testing