Reduce excessive logging when replica set primary is not reachable

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.9.1
    • Component/s: Cluster Management
    • None
    • None
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None

      When the primary is unreachable, the replica set health check happens every 10 ms instead of every 5000 ms (by default), and it logs at WARNING level for each server that's not reachable, flooding the logs.

      Driver should reduce logging to at most once per second for each server.

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

                Created:
                Updated:
                Resolved: