Network failures seen on Windows after upgrading to PyMongo 4.11

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.13.1
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Python Drivers
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      In PYTHON-4292 we changed the logic for timeout handling, in order to improve performance. In HELP-76100 it was reported that with PyMongo 4.11.2 there was an observed failure rate of 8 in 100 runs of: pymongo.errors.NetworkTimeout: XXX.com:27018: timed out with The operation did not complete (read) (_ssl.c:2580) measured at (sec)0.5 and short_timeout set to 0.5 (configured timeouts: connectTimeoutMS: 20000.0ms). The reporter confirmed that downgrading to PyMongo 4.10 resolves the issue.

      We attempted to reproduce the issue on a Windows host with the exact versions of PyMongo, Python and OpenSSL, but were unable to reproduce the failure.

      It seems the best recourse is to use the previous logic when on Windows, and use the new logic in PYTHON-4292 otherwise.

            Assignee:
            Steve Silvester
            Reporter:
            Steve Silvester
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: