Thanks Laura, We are using the CeleryExecutor. Just wondering if marking the TaskInstances as failed in metadata store would also work. -Raman
On 2018/04/12 16:27:00, Laura Lorenz <llor...@industrydive.com> wrote: > I use the CeleryExecutor and have used a mix of `celery control` and > messaging queue purges to kill the running tasks and prevent them from > being picked up by workers again (respectively), and doctor the DagRun to > failed to stop the scheduler from repopulating the message. I think if you > are using the Local or Sequential Executor you'd have to kill the scheduler > process. > > Laura > > On Thu, Apr 12, 2018 at 12:05 PM, Taylor Edmiston <tedmis...@gmail.com> > wrote: > > > I don't think killing a currently running task is possible today. > > > > Of course you can pause it from the CLI or web UI so that future runs don't > > get triggered, but it sounds like that's not what you're looking for. > > > > Best, > > Taylor > > > > *Taylor Edmiston* > > Blog <http://blog.tedmiston.com> | Stack Overflow CV > > <https://stackoverflow.com/story/taylor> | LinkedIn > > <https://www.linkedin.com/in/tedmiston/> | AngelList > > <https://angel.co/taylor> > > > > > > On Thu, Apr 12, 2018 at 11:26 AM, ramandu...@gmail.com < > > ramandu...@gmail.com > > > wrote: > > > > > Hi All, > > > We have a use case to cancel the already running DAG. So is there any > > > recommended way to do so. > > > > > > Thanks, > > > Raman > > > > > >
