[DRIVERS-2143] Application connections use connectTimeoutMS as the timeout for handshake commands Created: 04/Feb/20  Updated: 31/Mar/22

Status: Backlog
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Spec Change Priority: Minor - P4
Reporter: Shane Harvey Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Driver Changes: Needed

 Description   

Currently, application connections use connectTimeoutMS for the initial connection establishment and then use socketTimeoutMS as the timeout for all subsequent reads/writes. It may be more robust to use connectTimeoutMS for the initial isMaster handshake and authentication commands (instead of socketTimeoutMS) to detect failures quicker.

Note that this is lower priority because:

  1. The connection was just established so it should be rare for the initial isMaster to timeout.
  2. DRIVERS-555 Client Side Operation Timeout should eliminate this concern by unifying all timeouts.

Generated at Thu Feb 08 08:24:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.