[ 
https://issues.apache.org/jira/browse/HADOOP-14291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Loughran resolved HADOOP-14291.
-------------------------------------
    Resolution: Won't Fix

My cloudstore util already does more in terms of diagnostics than we can do in 
handling a single exception message. Closing as a wontfix

> S3a "Bad Request" message to include diagnostics
> ------------------------------------------------
>
>                 Key: HADOOP-14291
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14291
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>            Priority: Major
>
> There's a whole section in s3a troubleshooting because requests can get auth 
> failures for many reasons, including
> * no credentials
> * wrong credentials
> * right credentials, wrong bucket
> * wrong endpoint for v4 auth
> * trying to use private S3 server without specifying endpoint, so AWS being 
> hit
> * clock out
> * joda time
> ....
> We can aid with debugging this by including as much as we can in in the 
> message and a URL To a new S3A bad auth wiki page.
> Info we could include
> * bucket
> * fs.s3a.endpoint
> * nslookup of endpoint
> * Anything else relevant but not a security risk
> Goal; people stand a chance of working out what is failing within a bounded 
> time period



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Reply via email to