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 2019/07/20 20:26:53 UTC

[GitHub] [airflow] OmerJog commented on issue #4291: [AIRFLOW-1488] Add the TriggeredDagRunSensor operator

OmerJog commented on issue #4291: [AIRFLOW-1488] Add the TriggeredDagRunSensor operator
URL: https://github.com/apache/airflow/pull/4291#issuecomment-513496780
 
 
   @ashb I think the difference between what you are suggesting to what they are asking is that you an in fact force them to use sequential execution while the scenarios explained by them are not.
   I think you missed the `(max_active_dags=6)`  setting one slot in pool for two dags with many tasks isn't very practical.
   
   Also, I don't think your solution even work for what was described. 
   `my use case I run DAG A. task DAG_A_TASK_4 can't can't start if DAG_B is active.`
   so if you put `DAG_A_TASK_4` in same pool (1 slot) as ALL tasks in `DAG_B `  you won't get the desired outcome. For example the pool can be like:
   `DAG_B_TASK_1, DAG_B_TASK_2, DAG_A_TASK_4, DAG_B_TASK_3`
   Which is wrong because DAG_B didn't finish and DAG_A started.

----------------------------------------------------------------
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


With regards,
Apache Git Services