airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AIRFLOW-1018) Scheduler DAG processes can not log to stdout
Date Mon, 30 Oct 2017 19:41:00 GMT


ASF subversion and git services commented on AIRFLOW-1018:

Commit 4ee4e474b835b4f5f557226ba01b8cdfeb7d0789 in incubator-airflow's branch refs/heads/master
from [~bolke]
[;h=4ee4e47 ]

[AIRFLOW-1018] Make processor use logging framework

Until now, the dga processor had its own logging
making it hard to adjust for certain use cases
like working
in a container.

This patch moves everything to the standard
logging framework.

Closes #2728 from bolkedebruin/AIRFLOW-1018

> Scheduler DAG processes can not log to stdout
> ---------------------------------------------
>                 Key: AIRFLOW-1018
>                 URL:
>             Project: Apache Airflow
>          Issue Type: Bug
>    Affects Versions: 1.8.0
>         Environment: Airflow 1.8.0
>            Reporter: Vincent Poulain
>            Assignee: Bolke de Bruin
>            Priority: Blocker
>             Fix For: 1.9.0
> Each DAG has its own log file for the scheduler and we can specify the directory with
child_process_log_directory param. 
> Unfortunately we can not change device / by specifying /dev/stdout for example. That
is very useful when we execute Airflow in a container.
> When we specify /dev/stdout it raises:
> "OSError: [Errno 20] Not a directory: '/dev/stdout/2017-03-19'"

This message was sent by Atlassian JIRA

View raw message