[jira] [Commented] (HADOOP-13276) S3a operations keep retrying if the password is wrong

["Steve Loughran (JIRA)" <ji...@apache.org>]

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

Steve Loughran commented on HADOOP-13276:
-----------------------------------------

We're currently mapping bad signature -> 403 -> fail fast at our layer; if this (still) happens in the SDK, it's below our ability to deal with unless we can provide some retry logic there

> 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
(v7.6.3#76005)

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