Skip to content
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

Reduce boto connect/read timeouts [RHELDST-21242] #521

Merged
merged 1 commit into from
Nov 7, 2023

Conversation

negillett
Copy link
Member

The default value of connect_timeout and read_timeout in boto is 60 seconds. Our lambdas timeout after 15 seconds. There's no reason for the inner timeouts to exceed the outer and reducing the inner timeouts may prove more helpful in debugging.

The default value of connect_timeout and read_timeout in boto is 60
seconds. Our lambdas timeout after 15 seconds. There's no reason for the
inner timeouts to exceed the outer and reducing the inner timeouts may
prove more helpful in debugging.
@negillett
Copy link
Member Author

negillett commented Nov 2, 2023

Hold on this until CDN config changes are in place.
https://gitlab.cee.redhat.com/ansible-playbooks/exodus-cdn-playbooks/-/merge_requests/207

@@ -93,6 +110,8 @@ required:
- table
- config_table
- config_cache_ttl
- connect_timeout
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that adding these as "required" means it won't be backwards-compatible with existing config files so it will force an update in the playbooks at the same time. You might want to consider not adding them to required, or only adding them to required later.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that's why I've made this dependant on the cdn-playbooks change. Once that's fully deployed this will be safe.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or I guess they'd be deployed at the same time so it's probably safe just with the playbook change merged.

@negillett negillett merged commit 422a37b into release-engineering:master Nov 7, 2023
2 checks passed
@negillett negillett deleted the 21242 branch November 7, 2023 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants