hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Fabbri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15434) Upgrade to ADLS SDK that exposes current timeout
Date Wed, 02 May 2018 23:01:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-15434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461709#comment-16461709

Aaron Fabbri commented on HADOOP-15434:

The patch is trivial (one line bump to pom version).

Looked at some recent SDK changes:
 * 2.2.9. Add shouldRetry() logic and retry policy for requesting tokens from MSI.  Looks
ok. 404 is retry-able, for example. Max retry wait is 1+2+4+8=15 seconds.
 * 2.2.8. Default ADL request timeout from 5 to 60 seconds.
 * 2.2.7 Looks like support for different type of MSI endpoint (add support for GET as well
as POST). Improved exception text when getTokenSingleCall() gets an error response (even including
bytes of the response msg).

LGTM +1 based on your testing.


> Upgrade to ADLS SDK that exposes current timeout
> ------------------------------------------------
>                 Key: HADOOP-15434
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15434
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>            Priority: Major
>         Attachments: HADOOP-15434.001.patch
> HADOOP-15356 aims to expose the ADLS SDK base timeout as a configurable option in Hadoop,
but this isn't very testable without being able to read it back after the write logic has
been applied.

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