huozhanfeng opened a new pull request #16768:
URL: https://github.com/apache/airflow/pull/16768


   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   ---
   The log can't be shown normally when the task runs failed. Users can only 
get useless logs as follows. #13692
   
   <pre>
   *** Log file does not exist: 
/home/airflow/airflow/logs/dag_id/task_id/2021-06-28T00:00:00+08:00/28.log
   *** Fetching from: 
http://:8793/log/dag_id/task_id/2021-06-28T00:00:00+08:00/28.log
   *** Failed to fetch log file from worker. Unsupported URL protocol 
   </pre>
   
   The root cause is that scheduler will overwrite the info into the 
task_instance table in db when tasks into failed.  Webserver can't get the 
right host of the task from task_instance, because the hostname info is lost in 
the progress.
   
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to