You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "James Coder (JIRA)" <ji...@apache.org> on 2019/08/12 19:58:00 UTC
[jira] [Created] (AIRFLOW-5177) scheduler_job command passes
scheduler dag location
James Coder created AIRFLOW-5177:
------------------------------------
Summary: scheduler_job command passes scheduler dag location
Key: AIRFLOW-5177
URL: https://issues.apache.org/jira/browse/AIRFLOW-5177
Project: Apache Airflow
Issue Type: Bug
Components: scheduler
Affects Versions: 1.10.4, 1.10.3
Reporter: James Coder
There seems to be somewhere or inconsistency in one of these items. In my airflow set up the DAG location is not consistent across the scheduler and the workers. Meaning DAGS in the scheduler reside in /home/usr/airflow/... where as on my workers the DAGS may exist in /home/user/123... The issue I'm seeing is that when scheduler job call generate_commad, it uses SimpleDag, which only has full_filepath, and sends the command out with the -sd param as /home/usr/airflow..., then when the worker picks it up, it fails because the dag actually exists somewhere else (AIRFLOW_HOME is set as env variable).
It looks like it should replace /home/usr/airflow with DAGS_FOLDER/, or some other handling.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)