hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-14547) [WASB] the configured retry policy is not used for all storage operations.
Date Fri, 23 Jun 2017 20:42:00 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-14547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Steve Loughran updated HADOOP-14547:
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> [WASB] the configured retry policy is not used for all storage operations.
> --------------------------------------------------------------------------
>                 Key: HADOOP-14547
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14547
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>    Affects Versions: 2.9.0, 3.0.0-alpha4
>            Reporter: Thomas
>            Assignee: Thomas
>             Fix For: 2.9.0, 3.0.0-alpha4
>         Attachments: HADOOP-14547.001.patch
> 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.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message