[HADOOP-15076] Enhance S3A troubleshooting documents and add a performance document

• Type: Sub-task
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.8.2
• Fix Version/s: 3.1.0
• Component/s: documentation, fs/s3
• Target Version/s: 3.1.0, 3.0.2
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 30/Nov/17 10:14
• Updated: 28/Jun/19 20:19
• Resolved: 15/Feb/18 15:00

Description

A recurrent theme in s3a-related JIRAs, support calls etc is "tried upgrading the AWS SDK JAR and then I got the error ...". We know here "don't do that", but its not something immediately obvious to lots of downstream users who want to be able to drop in the new JAR to fix things/add new features

We need to spell this out quite clearlyi "you cannot safely expect to do this. If you want to upgrade the SDK, you will need to rebuild the whole of hadoop-aws with the maven POM updated to the latest version, ideally rerunning all the tests to make sure something hasn't broken.

Maybe near the top of the index.md file, along with "never share your AWS credentials with anyone"

Issue Links

• contains: HADOOP-14332 Document S3A SSE
• relates to: HADOOP-14531 [Umbrella] Improve S3A error handling & reporting