You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Josh Bacon (JIRA)" <ji...@apache.org> on 2018/02/09 17:38:00 UTC
[jira] [Commented] (AIRFLOW-1667) Remote log handlers don't upload
logs on task finish
[ https://issues.apache.org/jira/browse/AIRFLOW-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358749#comment-16358749 ]
Josh Bacon commented on AIRFLOW-1667:
-------------------------------------
+1 We are using CeleryExecutors and notice that our logs never ship unless we shut down our workers. Flush probably needs to happen on some interval or task event handler.
> Remote log handlers don't upload logs on task finish
> ----------------------------------------------------
>
> Key: AIRFLOW-1667
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1667
> Project: Apache Airflow
> Issue Type: Bug
> Components: logging
> Affects Versions: 1.9.0, 1.10.0
> Reporter: Arthur Vigil
> Priority: Major
>
> AIRFLOW-1385 revised logging for configurability, but the provided remote log handlers (S3TaskHandler and GCSTaskHandler) only upload on close (flush is left at the default implementation provided by `logging.FileHandler`). A handler will be closed on process exit by `logging.shutdown()`, but depending on the Executor used worker processes may not regularly shutdown, and can very likely persist between tasks. This means during normal execution log files are never uploaded.
> Need to find a way to flush remote log handlers in a timely manner, but without hitting the target resources unnecessarily.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)