Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-14831 Über-jira: S3a phase IV: Hadoop 3.1 features
  3. HADOOP-15076

Enhance S3A troubleshooting documents and add a performance document

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 2.8.2
    • 3.1.0
    • documentation, fs/s3
    • None

    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"

      Attachments

        1. HADOOP-15076-001.patch
          7 kB
          Steve Loughran
        2. HADOOP-15076-002.patch
          8 kB
          Steve Loughran
        3. HADOOP-15076-003.patch
          39 kB
          Steve Loughran
        4. HADOOP-15076-004.patch
          39 kB
          Steve Loughran
        5. HADOOP-15076-005.patch
          41 kB
          Steve Loughran
        6. HADOOP-15076-006.patch
          80 kB
          Steve Loughran

        Issue Links

          Activity

            People

              stevel@apache.org Steve Loughran
              stevel@apache.org Steve Loughran
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: