Skip to content
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.

Restart UI, Scheduler, Workers on detecting new DAGs in the DAG folder #9

Open
barney-s opened this issue Aug 6, 2018 · 3 comments
Labels
question Further information is requested

Comments

@barney-s
Copy link
Contributor

barney-s commented Aug 6, 2018

  1. Drain celery workers nodes and k8s executor pods to prepare for restart
  2. Restart airflow UI and Scheduler on detecting new DAGs in the DAG folder
@barney-s barney-s added the enhancement New feature or request label Aug 6, 2018
@pacuna
Copy link

pacuna commented Nov 16, 2018

Hi @barney-s , so right now what's the proper way of adding a new dag to the cluster?

@barney-s
Copy link
Contributor Author

There isnt unfortunately. Thinking restarting the workers would pull the latest. But not a clean solution.

@barney-s
Copy link
Contributor Author

@pacuna Did the config dag_dir_list_interval not help you ?
I believe thats the canonical way airflow supports refreshing DAGs.
https://cwiki.apache.org/confluence/display/AIRFLOW/Scheduler+Basics#Configuration

You can set that config using cluster.spec.config.airflow.
Set the env AIRFLOW__SCHEDULER__ DAG_DIR_LIST_INTERVAL

By default dags are refreshed every 5 minutes.

To enable continuous sync, use git or gcs dag source with once disabled.

barney-s added a commit to barney-s/airflow-operator that referenced this issue Nov 30, 2018
@barney-s barney-s added question Further information is requested and removed enhancement New feature or request labels Nov 30, 2018
barney-s added a commit that referenced this issue Nov 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants