You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What versions of the driver and its dependencies are you using? (Run cargo pkgid mongodb & cargo pkgid bson)
What version of MongoDB are you using? (Check with the MongoDB shell using db.version())
What is your MongoDB topology (standalone, replica set, sharded cluster, serverless)?
Describe the bug
Is there a plan to support the socket_timeout option? Our service has encountered a connection stuck issue. It's nice if this socket_timeout options is enabled and will solve our problem.
The text was updated successfully, but these errors were encountered:
Hi @fishincat, RUST-564 tracks adding support for this option. It is not currently planned, but I will discuss prioritizing this with the team. Feel free to follow that ticket for more updates.
We've investigated supporting that option and come to the conclusion that for technical reasons (see #1253 for details) it would require much more engineer time than expected; rather than that, we're going to be moving forward with implementing Client-Side Operation Timeout (see RUST-582) in the coming quarters which will cover this as well as a number of other use cases.
Versions/Environment
cargo pkgid mongodb
&cargo pkgid bson
)db.version()
)Describe the bug
Is there a plan to support the
socket_timeout
option? Our service has encountered a connection stuck issue. It's nice if thissocket_timeout
options is enabled and will solve our problem.The text was updated successfully, but these errors were encountered: