7445b03f51
This increases the timeout for a metadata request to something that should be easily satisfiable (50 seconds). But hopefully does so while still keeping the case of no-metadata service in mind. Previously, there was a small timeout and many retries (30) would be done. Now, - larger timeout (50 seconds) by default - retry until a given "max_wait" is reached (120 seconds default) The end result is that if we're hitting the timeout, there will only end up being a couple attempts made. But if the requests are coming back quickly then we'll still make several attempts. There is one EC2DataSource config change, now 'retries' is not used, but rather 'max_wait' to indicate generally how long it should try to find a metadata service.
16 lines
505 B
Plaintext
16 lines
505 B
Plaintext
# Documentation on data sources configuration options
|
|
datasource:
|
|
# Ec2
|
|
Ec2:
|
|
# timeout: the timeout value for a request at metadata service
|
|
timeout : 50
|
|
# The length in seconds to wait before giving up on the metadata
|
|
# service. The actual total wait could be up to
|
|
# len(resolvable_metadata_urls)*timeout
|
|
max_wait : 120
|
|
|
|
#metadata_url: a list of URLs to check for metadata services
|
|
metadata_urls:
|
|
- http://169.254.169.254:80
|
|
- http://instance-data:8773
|