[
https://issues.apache.org/jira/browse/AIRFLOW-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225625#comment-16225625
]
ASF subversion and git services commented on AIRFLOW-1018:
----------------------------------------------------------
Commit ef775d4f8aca13075eed7e207c07e5941ff68539 in incubator-airflow's branch
refs/heads/v1-9-test from [~bolke]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=ef775d4 ]
[AIRFLOW-1018] Make processor use logging framework
Until now, the dga processor had its own logging
implementation,
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
(cherry picked from commit 4ee4e474b835b4f5f557226ba01b8cdfeb7d0789)
Signed-off-by: Bolke de Bruin <[email protected]>
> Scheduler DAG processes can not log to stdout
> ---------------------------------------------
>
> Key: AIRFLOW-1018
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1018
> 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
(v6.4.14#64029)
