[HADOOP-14291] S3a "Bad Request" message to include diagnostics

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.8.0
• Component/s: fs/s3
• Assignee: Unassigned
• Reporter: Steve Loughran
• Created: 07/Apr/17 15:35
• Updated: 19/Feb/18 16:52
• Resolved: 19/Feb/18 15:37

Description

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

Issue Links

• relates to: HADOOP-14305 S3A SSE tests won't run in parallel: Bad request in directory GetFileStatus