Skip to content

Support for Client-Side Operation Timeout #5003

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

Open
gillesbergerp opened this issue Jun 15, 2025 · 2 comments
Open

Support for Client-Side Operation Timeout #5003

gillesbergerp opened this issue Jun 15, 2025 · 2 comments
Assignees
Labels
status: waiting-for-triage An issue we've not yet triaged

Comments

@gillesbergerp
Copy link

WHAT

Add support for MongoDb's client-side operation timeout (CSOT) which was introduced as an experimental feature in recent versions of the Sync as well as Reactive Streams Java drivers.

WHY

Operation timeouts are an essential tool to prevent long-running and/or expensive queries from impacting a cluster. Right now, it is possible to specify multiple timeout settings on a connection/client level as well as per operation (e.g., maxTimeMS). It would be beneficial to expand the control users have by allowing for overriding timeoutMS on a per-operation basis as wel..

REFERENCES

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jun 15, 2025
@mp911de mp911de self-assigned this Jun 16, 2025
@alexbevi
Copy link
Contributor

@gillesbergerp I love the idea. Might be worth looking into once the feature is no longer considered experimental.

@gillesbergerp
Copy link
Author

I am not aware of the precedence when it comes to supporting alpha features but would it be an option to introduce this in an experimental state already?
If that is acceptable, I can offer to prepare a pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-for-triage An issue we've not yet triaged
Projects
None yet
Development

No branches or pull requests

4 participants