You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/09/09 03:15:56 UTC
[GitHub] [airflow] dstandish opened a new issue, #26259: should we limit max queued dag runs for dataset-triggered dags
dstandish opened a new issue, #26259:
URL: https://github.com/apache/airflow/issues/26259
if a dataset-triggered dag is running, and upstreams are updated multiple times, many dag runs will be queued up because the scheduler checks frequently for new dag runs needed.
you can easily limit max active dag runs but cannot easily limit max queued dag runs. in the dataset case this represents a meaningful difference in behavior and seems undesirable.
i think it may make sense to limit max queued dag runs (for datasets) to 1. cc @ash @jedcunningham @uranusjr @blag @norm
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] ashb closed issue #26259: should we limit max queued dag runs for dataset-triggered dags
Posted by GitBox <gi...@apache.org>.
ashb closed issue #26259: should we limit max queued dag runs for dataset-triggered dags
URL: https://github.com/apache/airflow/issues/26259
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] ashb commented on issue #26259: should we limit max queued dag runs for dataset-triggered dags
Posted by GitBox <gi...@apache.org>.
ashb commented on issue #26259:
URL: https://github.com/apache/airflow/issues/26259#issuecomment-1242455362
> if a dataset-triggered dag is running, and upstreams are updated multiple times, many dag runs will be queued up because the scheduler checks frequently for new dag runs needed.
This is but design to my mind. Each time a dataset updates the a down stream dag run should be created to process that.
In future we can add some mechanism to give more control over this -- either using `catchup` flag, or some other mechanism that we've talked/hinted/thought about that works also let your control the all/any for multiple datasets.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] ashb commented on issue #26259: should we limit max queued dag runs for dataset-triggered dags
Posted by GitBox <gi...@apache.org>.
ashb commented on issue #26259:
URL: https://github.com/apache/airflow/issues/26259#issuecomment-1242475880
Oh! We already have `max_active_runs` on DAG but we aren't respecting that for dataset triggering! Ooos
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org