[JAVA-4048] Client Side Operations Timeout Created: 15/Mar/21  Updated: 12/Jan/24  Resolved: 11/Sep/23

Status: Closed
Project: Java Driver
Component/s: Retryability
Affects Version/s: None
Fix Version/s: None

Type: Epic Priority: Major - P3
Reporter: Esha Bhargava Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates JAVA-3828 Client Side Operations Timeout Implementing
Issue split
Upstream Changes Summary:

DRIVERS-555:
NA

Documentation Changes Summary: 1. What would you like to communicate to the user about this feature?
2. Would you like the user to see examples of the syntax and/or executable code and its output?
3. Which versions of the driver/connector does this apply to?

 Description   
Useful Info

Summary

Allow users to configure the timeout on operations by using a single timeout setting.

Motivation

Users have an array of options governing timeouts:
Driver timeouts: Server selection timeout, socket write timeout, socket read timeout, socket connect timeout
Server timeouts: maxTimeMS, maxAwaitTimeMS, wTimeout.
Users are often times unaware of the existence of all these settings and the effect they have on the timeout behavior of the driver and server. Due to this lack of awareness and understanding users often leave these settings at their defaults which is not necessarily what they desire in their timeout behaviors. Furthermore, timeout interaction with retryable writes compounds the situation. The timeout settings do not provide any clarity or reassurance of how long a user will wait for any given write or read.

We should also determine if the desired behavior should be, retry as many times as possible within the defined time period.

Cast of Characters

Lead: Jeff Yemin
Author: Divjot Arora
POCs: Java, C, Go, Swift
Product Owner:
 

Documentation

Scope Document
Technical Design



 Comments   
Comment by PM Bot [ 04/Feb/22 ]

If you are not logged in, you can view the tickets in this epic by following this link.

Generated at Thu Feb 08 09:01:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.