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

ClusterServerParameterRefresher can leave an open transaction on the CSRS after mongos shutdown.

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • CAR Team 2024-08-19, CAR Team 2024-09-02
    • 2

      This is usually not problematic since the reaper should kill it but if the reaper timeout is high this could cause other operations waiting on conflicting locks to wait on lock acquisition.

      See this comment for more details. 

      Either mongos can retry and make more of a best effort to abort transactions at shutdown or ClusterServerParameterRefresher can do it's work outside of a transaction as suggested.

       

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            kshitij.gupta@mongodb.com Kshitij Gupta
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: