[jira] [Commented] (AIRFLOW-1667) Remote log handlers don't upload logs on task finish

["Arthur Vigil (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16195609#comment-16195609 ] 

Arthur Vigil commented on AIRFLOW-1667:
---------------------------------------

AIRFLOW-1676 and AIRFLOW-1682 actually fix an underlying problem with the remote log handlers that was causing logs to _never_ be uploaded, so the problem isn't quite as bad as I thought. It would still be nice if we could replicate the behavior of the old logging system in getting task logs pushed in a timely manner as right now the timing is unpredictable.

> 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
>
> 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
(v6.4.14#64029)