Add configurable timeout for Execution API requests #56969
Merged
+32
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
ashb
reviewed
Oct 21, 2025
ashb
approved these changes
Oct 21, 2025
ron-gaist
approved these changes
Oct 21, 2025
kaxil
force-pushed
the
exec-timeout-conf
branch
from
41e871c to
f68feac
Compare
Workers can now configure the timeout for HTTP requests to the Execution API server via the `[workers] execution_api_timeout` configuration option. The default remains 5 seconds (httpx default) to preserve existing behavior. https://www.python-httpx.org/advanced/timeouts/ This prevents timeout errors in high-load environments where API servers may take longer than 5 seconds to respond. Users experiencing timeout issues can now increase this value without code changes. The timeout controls how long a worker waits for a single API request to complete, which is different from execution_api_retries that controls retry behavior after failures. Fixes apache#56571
kaxil
force-pushed
the
exec-timeout-conf
branch
from
f68feac to
fdbb9a7
Compare
potiuk
approved these changes
Oct 21, 2025
kaxil
added a commit
that referenced
this pull request
Oct 21, 2025
Workers can now configure the timeout for HTTP requests to the Execution API server via the `[workers] execution_api_timeout` configuration option. The default remains 5 seconds (httpx default) to preserve existing behavior. https://www.python-httpx.org/advanced/timeouts/ This prevents timeout errors in high-load environments where API servers may take longer than 5 seconds to respond. Users experiencing timeout issues can now increase this value without code changes. The timeout controls how long a worker waits for a single API request to complete, which is different from execution_api_retries that controls retry behavior after failures. Fixes #56571 (cherry picked from commit 0511604)
amoghrajesh
reviewed
Oct 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Workers can now configure the timeout for HTTP requests to the Execution API server via the
[workers] execution_api_timeoutconfiguration option. The default remains 5 seconds (httpx default) to preserve existing behavior.https://www.python-httpx.org/advanced/timeouts/
This prevents timeout errors in high-load environments where API servers may take longer than 5 seconds to respond. Users experiencing timeout issues can now increase this value without code changes.
The timeout controls how long a worker waits for a single API request to complete, which is different from
execution_api_retriesthat controls retry behavior after failures.Fixes #56571
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.