You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/10/30 19:41:00 UTC
[jira] [Commented] (AIRFLOW-1018) Scheduler DAG processes can not
log to stdout
[ https://issues.apache.org/jira/browse/AIRFLOW-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225622#comment-16225622 ]
ASF subversion and git services commented on AIRFLOW-1018:
----------------------------------------------------------
Commit 4ee4e474b835b4f5f557226ba01b8cdfeb7d0789 in incubator-airflow's branch refs/heads/master from [~bolke]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=4ee4e47 ]
[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
> 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)