Async server selection can take up to heartbeat frequency even when server becomes available sooner

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.11.1
    • Affects Version/s: None
    • Component/s: Async, Cluster Management
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There is a logic error in BaseCluster#selectServerAsync implementation. If the WaitQueueHandler is about to or already awaiting the next phase with the full heartbeat frequency timeout (default of 10 seconds) and a new request arrive to select a currently unavailable server, the wait queue handler is not notified, and therefore won't wake immediately to try to force a connection to the requested server.

              Assignee:
              Jeffrey Yemin
              Reporter:
              Jeffrey Yemin
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: