Improve ReplicaSetMonitor concurrency

XMLWordPrintableJSON

    • Type: Sub-task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      the SDAM spec mandates:

      "If some monitors block calling ismaster over slow connections, other monitors MUST proceed unimpeded"

      Currently the RSMW will block for an extended period while refreshing if an ismaster is slow for a single server. We should consider using a thread per-server (or possibly an event driven model).

              Assignee:
              Unassigned
              Reporter:
              Adam Midvidy (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: