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
Copy file name to clipboardExpand all lines: articles/storage/blobs/storage-retry-policy-java.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: pauljewellmsft
6
6
ms.author: pauljewell
7
7
ms.service: azure-blob-storage
8
8
ms.topic: how-to
9
-
ms.date: 04/29/2024
9
+
ms.date: 05/03/2024
10
10
ms.custom: devx-track-java, devguide-java
11
11
---
12
12
@@ -26,7 +26,7 @@ The following table lists the parameters available when constructing a [RequestR
26
26
| --- | --- | --- | --- |
27
27
|`retryPolicyType`|[RetryPolicyType](/java/api/com.azure.storage.common.policy.retrypolicytype)| Optional. The approach to use for calculating retry delays. |[EXPONENTIAL](/java/api/com.azure.storage.common.policy.retrypolicytype#com-azure-storage-common-policy-retrypolicytype-exponential)|
28
28
|`maxTries`| Integer | Optional. The maximum number of retry attempts before giving up. | 4 |
29
-
|`tryTimeoutInSeconds`| Integer | Optional. Maximum time allowed before a request is cancelled and assumed failed. This value should be based on the bandwidth available to the host machine and proximity to the Storage service. A good starting point might be 60 seconds per MB of anticipated payload size. | Integer.MAX_VALUE (seconds) |
29
+
|`tryTimeoutInSeconds`| Integer | Optional. Maximum time allowed before a request is cancelled and assumed failed. Note that the timeout applies to the operation request, not the overall operation end to end. This value should be based on the bandwidth available to the host machine and proximity to the Storage service. A good starting point might be 60 seconds per MB of anticipated payload size. | Integer.MAX_VALUE (seconds) |
30
30
|`retryDelayInMs`| Long | Optional. Specifies the amount of delay to use before retrying an operation. | 4ms for [EXPONENTIAL](/java/api/com.azure.storage.common.policy.retrypolicytype#com-azure-storage-common-policy-retrypolicytype-exponential), 30ms for [FIXED](/java/api/com.azure.storage.common.policy.retrypolicytype#com-azure-storage-common-policy-retrypolicytype-fixed)|
31
31
|`maxRetryDelayInMs`| Long | Optional. Specifies the maximum delay allowed before retrying an operation. | 120ms |
32
32
|`secondaryHost`| String | Optional. Secondary storage account endpoint to retry requests against. Before setting this value, you should understand the issues around reading stale and potentially inconsistent data. To learn more, see [Use geo-redundancy to design highly available applications](../common/geo-redundant-design.md)| None |
@@ -43,7 +43,7 @@ BlobServiceClient client = new BlobServiceClientBuilder()
43
43
```
44
44
45
45
46
-
In this example, each service request issued from the `BlobServiceClient` object uses the retry options as defined in the `RequestRetryOptions` instance. You can configure various retry strategies for service clients based on the needs of your app.
46
+
In this example, each service request issued from the `BlobServiceClient` object uses the retry options as defined in the `RequestRetryOptions` instance. This policy applies to client requestsYou can configure various retry strategies for service clients based on the needs of your app.
0 commit comments