Monitoring should not be immediately scheduled on streaming failure

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.0
    • Affects Version/s: 3.6.0
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When some error occurs once the driver has started streaming topology updates, the driver currently uses the interruptable async timer's immediate options in order to reschedule monitoring immediately. We need to ensure that there is some time between attempts in these error cases, as its likely that if the error closed the connection then an immediate attempt to reconnect is likely to fail.

              Assignee:
              Matt Broadstone
              Reporter:
              Matt Broadstone
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: