-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Fix retry_exponential_backoff
divide by zero error when retry delay is zero
#17003
Fix retry_exponential_backoff
divide by zero error when retry delay is zero
#17003
Conversation
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
|
15dbe99
to
48bd9dd
Compare
retry_exponential_backoff
divide by zero error when retry delay is zeroretry_exponential_backoff
divide by zero error when retry delay is zero
fef1c54
to
cec61c0
Compare
This test was incorrect before. When `delay.total_seconds()` equals 1 and `self.try_number` equals 1, `min_backoff` equals 1. Thus, `modded_hash` always equals 1, regardless of the value of `ti_hash`. So it should not be a period of 1 to 15 seconds, but just 1 second. Code referenced was: airflow/airflow/models/taskinstance.py Lines 1064 to 1087
The test can be reused as the end result is the same.
cec61c0
to
b5acb5b
Compare
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
When
retry_delay
is zero, theretry_exponential_backoff
algorithm has a divide-by-zero error in themodded_hash
calculation, which causes the scheduler to crash.d1dceff attempted to address the divide-by-zero error by adding a ceiling function, but it doesn't account for this particular edge case. Using a lower bound instead would be a better implementation.
Fixes #17005.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.