[HADOOP-14248] Retire SharedInstanceProfileCredentialsProvider in trunk.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha4
• Fix Version/s: 3.0.0-alpha4
• Component/s: fs/s3
• Target Version/s: 3.0.0-alpha4
• Hadoop Flags: Incompatible change, Reviewed
• Release Note: SharedInstanceProfileCredentialsProvider is removed after this change. Users should use InstanceProfileCredentialsProvider provided by AWS SDK instead, which itself enforces a singleton instance to reduce calls to AWS EC2 Instance Metadata Service.
• Assignee: Mingliang Liu
• Reporter: Mingliang Liu
• Created: 28/Mar/17 00:03
• Updated: 17/Apr/17 15:44
• Resolved: 12/Apr/17 17:12

Description

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.

Issue Links

• is related to: HADOOP-14301 Deprecate SharedInstanceProfileCredentialsProvider in branch-2.
• relates to: HADOOP-13050 Upgrade to AWS SDK 1.11.45
• relates to: HADOOP-13727 S3A: Reduce high number of connections to EC2 Instance Metadata Service caused by InstanceProfileCredentialsProvider.
• relates to: HADOOP-14237 S3A Support Shared Instance Profile Credentials Across All Hadoop Nodes