-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EC2MetadataUtils is very slow after 1.11.678 #2276
Comments
Moreover, nothing was mentioned about this modification on the 1.11.678 release notes. https://github.com/aws/aws-sdk-java/blob/master/CHANGELOG.md#111678-2019-11-19 |
Tried |
Hi @kliakos yes, this is related to the Instance Metadata Service V2 change, we have multiple reports of increased latency when calling the new service. We've opened an internal ticket to the EC2 team behind the Metadata Service and they are investigating. Not mentioning this change in the CHANGELOG was a miss in our part. I'll update here when we hear back from the EC2 team. |
Hi! Any updates on this one? I'm also having intermittent latency issues (sometimes reaching the non-configurable 1sec read timeout) while the SDK is fetching credentials from IMDS. |
Has there been any improvement with this issue? I tried |
Hi! I talked about this issue and described our custom solution in this article. |
|
There's no recent reports of IMDSv2 high latency, so I'll go ahead and close this. If you are still seeing intermittent latency issues, please test a more recent version of the SDK 1.12.x, and then open a new fresh issue with repro steps. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
On 1.11.678 release, the
EC2CredentialsUtils
was replaced withInstanceMetadataServiceResourceFetcher
.A call to
EC2MetadataUtils.getInstanceInfo()
which used to last a few milliseconds, now takes a few seconds! On 1.11.678 it takes 10 seconds to respond, while on 1.11.749 it is quite better, but still it takes 2 seconds.Is this something related to Metadata Service Version 2, or the SDK itself? If this is by design the way it works and the latency issue can not be fixed, we should at least be given the option to use the v1 service via the SDK.
The text was updated successfully, but these errors were encountered: