hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-15076) s3a troubleshooting to add "things don't work after I dropped in a new AWS SDK JAR"
Date Thu, 11 Jan 2018 18:26:00 GMT

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

Steve Loughran updated HADOOP-15076:
    Attachment: HADOOP-15076-003.patch

HADOOP-15076 patch 003

* add something on the SDK message "you aborted the file", tell people to ignore it.
* Move all performance related content into its own document, one focused on performance and
structured in  way which should hold together.
* Added a section on distcp settings and options.

The goal of the perf section is to split the core docs into 3
# get it to work (index)
# get it to work fast (perf)
# why doesn't it work (troubleshooting)

crosslinking to each other + s3guard + committers

> s3a troubleshooting to add "things don't work after I dropped in a new AWS SDK JAR"
> -----------------------------------------------------------------------------------
>                 Key: HADOOP-15076
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15076
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: documentation, fs/s3
>    Affects Versions: 2.8.2
>            Reporter: Steve Loughran
>            Assignee: Abraham Fine
>         Attachments: HADOOP-15076-001.patch, HADOOP-15076-002.patch, HADOOP-15076-003.patch
> 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
> Maybe near the top of the index.md file, along with "never share your AWS credentials
with anyone"

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message