Fix mongobridge's limitations with restarted nodes

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Do
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • ALL
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      As described in comments added in SERVER-77987 as well as in this comment , mongobridge may not do a good job of detecting that a node was restarted. For example, when mongobridge is being used between some Node A and Node B, on restarting Node B mongobridge will not aggressively close its connection with Node A, leading Node A to think the connection with Node B is still healthy.

            Assignee:
            Unassigned
            Reporter:
            Huayu Ouyang
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: