[
https://issues.apache.org/jira/browse/HADOOP-16660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968190#comment-16968190
]
Sneha Vijayarajan commented on HADOOP-16660:
--------------------------------------------
Test Results: From East US accounts.
Namespace not enabled:
{code:java}
[INFO] Results:
[INFO]
[INFO] Tests run: 42, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[WARNING] Tests run: 396, Failures: 0, Errors: 0, Skipped: 211
[INFO]
[WARNING] Tests run: 192, Failures: 0, Errors: 0, Skipped: 126{code}
Namespace enabled:
{code:java}
[INFO] Results:
[INFO]
[INFO] Tests run: 42, Failures: 0, Errors: 0, Skipped: 0
[ERROR] Errors:
[ERROR] ITestAzureBlobFileSystemCLI>AbstractAbfsIntegrationTest.setup:137 »
AbfsRestOperation
[INFO]
[ERROR] Tests run: 396, Failures: 0, Errors: 1, Skipped: 25
[WARNING] Tests run: 192, Failures: 0, Errors: 0, Skipped: 126
{code}
The failing test needs to be rewritten as it has not taken into consideration
namespace enabled account scenario. Jira raised to handle this:
https://issues.apache.org/jira/browse/HADOOP-16687
> ABFS: Make RetryCount in ExponentialRetryPolicy Configurable
> ------------------------------------------------------------
>
> Key: HADOOP-16660
> URL: https://issues.apache.org/jira/browse/HADOOP-16660
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Reporter: Sneha Vijayarajan
> Assignee: Sneha Vijayarajan
> Priority: Major
> Fix For: 3.3.0
>
>
> ExponentialRetryPolicy will retry requests 30 times which is the default
> retry count in code whe HttpRequests fail.
> If the client too has re-try handling, the process seems hanged to the client
> App due to the high number of retries. This Jira aims to provide a config
> control for retry count.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
