DOCSP-26065: socketTimeoutMS behavior

[rustagir]

Pull Request Info

PR Reviewing Guidelines

JIRA - DOCSP-26065
Staging - FAQ

Self-Review Checklist

• Is this free of any warnings or errors in the RST?
• Did you run a spell-check?
• Did you run a grammar-check?
• Are all the links working?

[ccho-mongodb]

This version looks much better, thanks for making the changes! Mostly minor suggestions, would like to take a quick look after you've made the updates.

[ccho-mongodb]

Suggestion:

I think, but am not sure, that this refers to the disconnect as the failure and not some other type of write failure. If so, it would be helpful to describe it as a disconnect since that may not be similar to a general failure.

Suggested change

	inconsistencies if your application retries the operation after failure.
	inconsistencies if your application retries the operation after a disconnection.

[ccho-mongodb]

Suggestion:

I think it could be helpful to describe the process as a "MongoDB" one as done earlier since it's a general term.

I think it's not a definite outcome that the driver will successfully close it as something else could go wrong.

Suggested change

	process times out, the driver will successfully close the socket. We
	MongoDB process times out, the driver will close the socket. We

[ccho-mongodb]

LGTM! I think there's a run-on sentence that could be broken up, but no need for another review.

[ccho-mongodb]

Issue:

I think this is a run-on sentence.

Suggestion:

I think this is what was intended:

Suggested change

	Starting in {+mdb-server+} version 4.2, the server terminates
	certain operations such as aggregations and find operations if the
	client disconnects the operations successfully completes. To see a full
	Starting in {+mdb-server+} version 4.2, when the client disconnects before
	completing certain operations, such as aggregation and find operations,
	the server automatically terminates them.

[rustagir]

eliminated a clause to shorten

[ccho-mongodb]

Suggestion:
Could be helpful to identify that this is the explicit server behavior.

Suggested change

	Other operations, such as write operations, continue to run on the
	{+mdb-server+} even if the client disconnects. This behavior can cause data
	The server allows other operations, such as write operations, to continue to run on the
	{+mdb-server+} even if the client disconnects. This behavior can cause data

[rustagir]

Not changing because it seems like the mechanism is not that the server "allows" certain operations to continue running, but rather that it marks certain operations for termination.