Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DRIVERS-2884 Avoid connection churn when operations timeout #1675

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

prestonvasquez
Copy link
Contributor

Please complete the following before merging:

  • Update changelog.
  • Make sure there are generated JSON files from the YAML test files.
  • Test changes in at least one language driver.
  • Test these changes against all server versions and topologies (including standalone, replica set, sharded
    clusters, and serverless).

data:
failCommands: ["insert"]
blockConnection: true
blockTimeMS: 750
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I worry that these tests rely on the undocumented behavior of failCommand+blockTimeMS with maxTimeMS. What if the server decides to enforce maxTimeMS even inside failCommand?

eventType: cmap
events:
- connectionClosedEvent:
reason: error
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this case result in the connection being closed? I propose the connection remain pending for as many operations as it takes to read the response up to some reasonably small limit like 1-5 seconds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants