[GitHub] [airflow] jpmsilva commented on issue #9975: max_active_runs = 1 can still create multiple active execution runs

[GitBox <gi...@apache.org>]

jpmsilva commented on issue #9975:
URL: https://github.com/apache/airflow/issues/9975#issuecomment-808386108


   Hi there
   We are facing a similar issue: we have a DAG that runs to make a system consistent. We want to trigger this DAG via the stable REST API when certain things happen on a separate system. Because the DAG makes the system consistent, regardless when it runs, we want to have at most one instance running, and another queued. If there is a queued DAGRun, there is no point in queueing another, since the queued DAGRun will make the system eventually consistent.
   We were hoping to use max_active_runs to control how many DAGRuns for a DAG exist in the running state, but it looks like it doesn't work this way.
   The DAG in question is not scheduled: it is always meant to be triggered manually via the stable REST API.
   It looks like a new DAGRun state "queued" would be needed to achieve this, as mentioned previously.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org