[HADOOP-14547] [WASB] the configured retry policy is not used for all storage operations.

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.0, 3.0.0-alpha4
• Fix Version/s: 2.9.0, 3.0.0-alpha4
• Component/s: fs/azure
• Target Version/s: 2.9.0, 3.0.0-alpha4
• Assignee: Thomas Marqardt
• Reporter: Thomas Marqardt
• Created: 19/Jun/17 23:11
• Updated: 28/Jun/17 15:52
• Resolved: 23/Jun/17 20:41

Description

There are a few places where the WASB retry policy was not used, and instead the Azure Storage SDK default retry policy was used. These places include some calls to blob.exist(), container.exists(), blob.delete(), and operations with secure mode enabled (fs.azure.secure.mode = true).

You can set a break point on com.microsoft.azure.storage.core.ExecutionEngine.executeWithRetry in the Azure Storage SDK and see that the WASB configured retry policy (DEFAULT_MAX_RETRY_ATTEMPTS, etc.) is not used.

Issue Links

• is depended upon by: HADOOP-14552 Über-jira: WASB client phase II: performance and testing