Darragh
06/11/2020, 5:34 PMDylan
06/11/2020, 5:38 PMCancelled
state follows a “best attempt” design pattern. It’s extremely difficult to kill arbitrary python processes, especially ones that are running on shared Dask Clusters or the like. Here’s the PR where we added the “cancellation lite” functionality to Prefect Server (which I believe you’re using): https://github.com/PrefectHQ/prefect/pull/2535Cancelled
state may not stop the run immediately, but it should stop any new Task Runs from starting. Once Running
Task Runs enter a Finished state, the flow run should stopDarragh
06/11/2020, 5:40 PMDylan
06/11/2020, 5:41 PMCancelled
state
2. Interact with Fargate to delete the run infrastructureMarvin
06/11/2020, 5:46 PMDarragh
06/11/2020, 5:50 PMDylan
06/11/2020, 5:52 PMRunning
state to resolve on their ownDarragh
06/11/2020, 5:54 PMDylan
06/11/2020, 5:57 PMRunning
Task Run to stop, you’ll need to kill its execution infrastructure manuallyDarragh
06/11/2020, 5:58 PMDylan
06/11/2020, 5:58 PMRunning
Task Runs enter finished states, then setting the Flow Run to Cancelled
will do the trickPedro Machado
06/11/2020, 8:57 PMDylan
06/11/2020, 8:57 PMPedro Machado
06/11/2020, 9:00 PMDylan
06/11/2020, 9:01 PMPedro Machado
06/11/2020, 9:02 PMCancelled
or is there a way to send a signal to a task that is already running to tell it to stop? This would not work if the task is hung but if it's running as expected, it could decide that it needs to stop because the external signal was sent.Dylan
06/12/2020, 3:12 PMDarragh
06/12/2020, 7:28 PMDylan
06/12/2020, 7:28 PM