You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/06/24 09:26:16 UTC
[jira] [Updated] (HADOOP-13319) S3A to list
InstanceProfileCredentialsProvider after
EnvironmentVariableCredentialsProvider
[ https://issues.apache.org/jira/browse/HADOOP-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-13319:
------------------------------------
Attachment: HADOOP-13252-branch-2-001.patch
Patch 001. Flips the order of creation.
full test run against s3 ireland
> S3A to list InstanceProfileCredentialsProvider after EnvironmentVariableCredentialsProvider
> -------------------------------------------------------------------------------------------
>
> Key: HADOOP-13319
> URL: https://issues.apache.org/jira/browse/HADOOP-13319
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: HADOOP-13252-branch-2-001.patch
>
>
> S3A now has a default list of credential providers to pick up AWS credentials from
> The environment variable provider added in HADOOP-12807 should go before the {{InstanceProfileCredentialsProvider}} one in the list, as it does a simple env var checkup. In contrast {{InstanceProfileCredentialsProvider}} does an HTTP request *even when not running on EC2*. It may block for up to 2s to await a timeout, and network problems could take longer.
> Checking env vars is a low cost operation that shouldn't have to wait for a network timeout before being picked up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org