-
Type: Sub-task
-
Resolution: Fixed
-
Priority: Unknown
-
Affects Version/s: None
-
Component/s: Client Side Operations Timeout
-
None
-
Java Drivers
-
Not Needed
-
Description: Currently, there is an inconsistency in how timeout-related exceptions are handled in our codebase. Specifically, the method hasExpired is checked in
throwTranslatedWriteException, while hasTimeoutMS is checked the translateReadException method. This discrepancy was noted during a review where it was observed that we should not check for onExpired when a MongoSocketWriteTimeoutException is caught. If a timeout exception from the socket occurs and timeoutMS is enabled, it indicates that a CSOT (Client-Side Operation Timeout) has occurred.
This ticket aims to unify the logic across these methods to ensure consistent handling of timeout exceptions.