Details
-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
None
-
None
-
1
Description
KV operations do not fast-fail when the operation timeout has been reached, whether the timeout is provided by application code, or the default operation timeout is used.
- Config.SendTimeout (default of 15 seconds) is the primary wait if there is lag / no response from the server
- Pending operations are only removed after the SendTimeout has elapsed (15 seconds) which means they go down the successful path
- Operation.Timeout is only checked after a result has been received and to determine if a failed request can be retried
KV operations should use the provided timeout value and fast-fail with a SendTimeoutException. When a timeout occurs, it should be removed from the pending operations list, so if a server response is received later it is not treat as successful.
Attachments
Issue Links
- is triggering
-
NCBC-1784 ThresholdLoggingTracer throws System.ArgumentNullException during processing
- Resolved
-
NCBC-1786 2.7.0 candidate .net async mode - Throughput gradually goes down through the test
- Resolved
-
NCBC-1787 2.7.0 candidate .net async mode - half the time connection not recovering after 1 node swap rebalance
- Resolved
-
NCBC-1788 2.7.0 candidate .net async mode - after drop connection and reconnected, sdk does not recover
- Resolved