You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2019/02/04 11:17:00 UTC

[jira] [Commented] (HADOOP-15573) s3guard set-capacity to not retry on an access denied exception

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

Steve Loughran commented on HADOOP-15573:
-----------------------------------------

as per [~adam.antal]'s comment, closing as fixed in 3.2.0

> s3guard set-capacity to not retry on an access denied exception
> ---------------------------------------------------------------
>
>                 Key: HADOOP-15573
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15573
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Steve Loughran
>            Priority: Minor
>
> when you call {{hadoop s3guard set-capacity}} with restricted access, you are (correctly) blocked by AWS, but the client keeps retrying. It should fail fast on a 400/AccessDenied



--
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