-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Log execution API server URL at task startup #57343
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
Conversation
jscheffl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good for me. The title anticipated "Move" but I see "Add - is the log to be deleted on some other place?
Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
7a48d04 to
edd63b6
Compare
Nope, no deletions anywhere. I could delete in "execute_workload.py" to avoid duplicates, will send a PR to do that |
(cherry picked from commit cd32d1b) Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
(cherry picked from commit cd32d1b) Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
There could be cases when custom executors (edge for example faced it), where we do not log where the worker is trying to connect during task startup time.
Edge: https://github.com/apache/airflow/blob/main/providers/edge3/src/airflow/providers/edge3/cli/worker.py#L188-L204
VS celery / KE: https://github.com/apache/airflow/blob/main/task-sdk/src/airflow/sdk/execution_time/execute_workload.py#L58-L64
I figured it is better to have double logs for debugging than none. I could remove it for celery / KE and rest if needed, but this one is more important.
^ 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.