Avoid swallowing Interruption errors when invoking setLastOpToSystemLastOpTime() on command handlers

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • 3
    • TBD
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-75548  modified pre-existing invocations to ReplClientInfo::setLastOpToSystemLastOpTime() within  _configsvrRemoveShard and _configsvrTransitionToDedicatedConfigServer  by wrapping them into a try/catch block.

      While this change allows mongod nodes from being terminated upon a node step down (because an Interrupted exception was raised from the destructor of a ScopeGuard), it does not allow the interruption to be returned back to the caller.

              Assignee:
              Unassigned
              Reporter:
              Paolo Polato
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: