Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-60016

serverStatus and collection stats should not block on the RSTL lock

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.0.0-rc0, 5.0.14
    • 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

    Description

      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. 

      Attachments

        Issue Links

          depends on

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-63219 Change collStats cmd to run without the RSTL lock so FTDC can continue to report during repl state changes

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Task - A task that needs to be done. SERVER-64053 Support optionally skipping the RSTL lock in AutoGetOplog

          • Major - P3 - Major loss of function.
          • Backlog

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-63264 Create a way to have serverStatus output all sections for testing

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              dianna.hohensee@mongodb.com Dianna Hohensee
              dianna.hohensee@mongodb.com Dianna Hohensee
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: