Boris, Thank you for your response, however that doesn't quite work for me;
I would (also) need a pool for each job I run and don't actually want to
queue new jobs if one is already running.
Hakan, This is pretty much exactly what I was looking for! I'm curious what
your session_scope() function l
Nik,
I had a similar problem and I solved it by querying the dagrun table to
make sure a dag is not running and kick it off with the TriggerDagRun. It
has been running for months now without any issues so I highly recommend it.
I added a utility function and I call that before I do the trigger. H
Hi Nik, looks like you experience the same problem I had
https://lists.apache.org/thread.html/%3ccanrt7t1te7ei82nvry-yeubu2-g4ax3gsdtl3rnxyhj2q-q...@mail.gmail.com%3E
Bolke suggested to use a pool to ensure only one instance is running.
Max active run affects only scheduled jobs so triggered ones
I'm using the TriggerDagRunOperator within a Sensor DAG to automatically
sense and start loads, however the problem I'm coming across, given that I
want to run this Sensor DAG often (every 5 minutes), is the same run can be
triggered multiple times. Is there a way to avoid this? I've set
max_active
