-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
[AIRFLOW-6177] Log DAG processors timeout event at error level, not info #6731
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6731 +/- ##
==========================================
- Coverage 84.54% 84.54% -0.01%
==========================================
Files 669 669
Lines 37738 37738
==========================================
- Hits 31907 31904 -3
- Misses 5831 5834 +3
Continue to review full report at Codecov.
|
|
@XD-DENG It is already logged at the default level (since it's Info), this is more just to make it more obvious that something is going wrong -- if a user sees this in their logs it is a sign of problems (dag file is too complex, not enough resources for scheduler etc) so error level makes sense. |
Get it. Thanks @ash for the clarification. Let’s have a JIRA for this before we merge then. |
Super I will file one now :-) |
e924262
to
ca85eaa
Compare
This case prevents a DAG from being scheduled so should be an error.
ca85eaa
to
5755d33
Compare
Merged. Thanks @robinedwards |
…nfo (apache#6731) This case prevents a DAG from being scheduled so should be an error.
This case prevents a DAG from being scheduled by the scheduler so should be an error to make troubleshooting easier.
https://issues.apache.org/jira/browse/AIRFLOW-6177