You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Session Consistency: Adds SessionTokenMismatchRetryPolicy optimization through customer supplied region switch hints (#5128)
This PR will allow application developers to configure hints through a
SessionRetryOptions instance which will signal to the SDK whether to pin
retries on the local region or move quicker to a remote region when
READ_SESSION_NOT_AVAILABLE errors are thrown.
[] New feature (non-breaking change which adds functionality)
---------
Co-authored-by: Fabian Meiswinkel <fabianm@microsoft.com>
/// Sets the minimum retry time for 404/1002 retries within each region for read and write operations.
25
+
/// The minimum value is 100ms - this minimum is enforced to provide a way for the local region to catch-up on replication lag. The default value is 500ms - as a recommendation ensure that this value is higher than the steady-state
26
+
/// replication latency between the regions you chose
/// Sets the maximum number of retries within each region for read and write operations. The minimum value is 1 - the backoff time for the last in-region retry will ensure that the total retry time within the
32
+
/// region is at least the min. in-region retry time.
33
+
/// </summary>
34
+
publicintMaxInRegionRetryCount{get;privateset;}
35
+
36
+
/// <summary>
37
+
/// hints which guide SDK-internal retry policies on how early to switch retries to a different region. If true, will retry all replicas once and add a minimum delay before switching to the next region.If false, it will
/// intent is If a client specify a value, we will force it to be atleast 1, otherwise default is going to be 1(right now both the values are 1 but we have the provision to change them in future).
0 commit comments