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] [Commented] (HADOOP-13276) S3a operations keep retrying if the password is wrong
Date Mon, 20 Nov 2017 15:07:00 GMT

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

Steve Loughran commented on HADOOP-13276:

nothing in particular. We are about to enhance our retry logic within the HADOOP-13786 patch,
& should look at it in this context. We don't want our retry logic there to amplify the
problem either. Looking at the code there, it holds. That is, S3ARetryPolicy treats 403 as
unrecoverable. That's what I'd like all the way down (though I presume the IAM authenticator
tries to reacquire some fresh session credentials, doesn't it? So one retry probably makes

> S3a operations keep retrying if the password is wrong
> -----------------------------------------------------
>                 Key: HADOOP-13276
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13276
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Steve Loughran
>            Assignee: Thomas Poepping
>            Priority: Minor
> If you do a {{hadoop fs}} command with the AWS account valid but the password wrong,
it takes a while to timeout, because of retries happening underneath.
> Eventually it gives up, but failing fast would be better.
> # maybe: check the password length and fail if it is not the right length (is there a
standard one? Or at least a range?)
> # consider a retry policy which fails faster on signature failures/403 responses

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