Heartbeat socket settings for MongoClientSettings should have non-infinite read timeout

XMLWordPrintableJSON

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

      The legacy MongoClient defaults the heartbeat socket settings to a 20 sec connect timeout and a 20 second read timeout.

      MongoClientSettings should similarly ensure that the default timeouts are not infinite.

      Given the SDAM spec it's possible that MongoClientSettings shouldn't even expose heartbeat socket settings, instead just using the normal socket settings connect timeout. Have to consider backwards compatibility with the existing async MongoClientSettings, and weight that against what API we want to offer going forward.

              Assignee:
              Ross Lawley
              Reporter:
              Jeffrey Yemin
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: