[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hadoop-dev
Subject:    [jira] [Created] (HADOOP-14248) Retire SharedInstanceProfileCredentialsProvider after AWS SDK upgrad
From:       "Mingliang Liu (JIRA)" <jira () apache ! org>
Date:       2017-03-28 0:03:41
Message-ID: JIRA.13059583.1490659405000.137960.1490659421662 () Atlassian ! JIRA
[Download RAW message or body]

Mingliang Liu created HADOOP-14248:
--------------------------------------

             Summary: Retire SharedInstanceProfileCredentialsProvider after AWS SDK \
upgrade  Key: HADOOP-14248
                 URL: https://issues.apache.org/jira/browse/HADOOP-14248
             Project: Hadoop Common
          Issue Type: Sub-task
          Components: fs/s3
    Affects Versions: 3.0.0-alpha3
            Reporter: Mingliang Liu
            Assignee: Mingliang Liu


This is from the discussion in [HADOOP-13050].

So [HADOOP-13727] added the SharedInstanceProfileCredentialsProvider, which \
effectively reduces high number of connections to EC2 Instance Metadata Service \
caused by InstanceProfileCredentialsProvider. That patch, in order to prevent the \
throttling problem, defined new class {{SharedInstanceProfileCredentialsProvider}} as \
a subclass of {{InstanceProfileCredentialsProvider}}, which enforces creation of only \
a single instance.

Per [HADOOP-13050], we upgraded the AWS Java SDK. Since then, the \
{{InstanceProfileCredentialsProvider}} in SDK code internally enforces a singleton. \
That  confirms that our effort in [HADOOP-13727] makes 100% sense. Meanwhile, \
{{SharedInstanceProfileCredentialsProvider}} can retire gracefully in trunk branch.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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


[prev in list] [next in list] [prev in thread] [next in thread]