-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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-6040] ReadTimeoutError should not raise exception #7616
Conversation
continuation of #6643 |
a50887d
to
5658156
Compare
5658156
to
6f61cdb
Compare
@dimberman I do not fully agree with making this a warning. Warnings often confuse people and this read timeout is totally expected. I would even demote it to debug because we would only look into this if something is fishy anyways. |
I don't think this is the right approach for fixing AIRFLOW-6040. The Watcher isn't being ran in its own thread so it must timeout so it's not blocking further execution. Therefor it's not an error or a warning as this is the expected behavior you're looking for. |
@maxirus While I agree with this being the wrong approach to fix the issue, I beg to differ: Yes, it is not run in a separate thread. But it is run in a separate process. |
Issue link: AIRFLOW-6040
Make sure to mark the boxes below before creating PR: [x]
[AIRFLOW-NNNN]
. AIRFLOW-NNNN = JIRA ID** For document-only changes commit message can start with
[AIRFLOW-XXXX]
.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.
Read the Pull Request Guidelines for more information.