Tim Helfensdörfer
05/31/2022, 8:55 AMAnna Geller
05/31/2022, 9:37 AMhttps://media.giphy.com/media/LG4usXVLfNDRSalw3P/giphy.gif▾
ps -ef | grep python
kill -s SIGTERM PID
ps -ef | grep prefect
kill -s SIGTERM PID
Tim Helfensdörfer
05/31/2022, 9:40 AMAnna Geller
05/31/2022, 9:51 AMstill marked as "Running" in the interface.we have an open issue for it, it's on the roadmap I understand your point but this is indeed a bit more complicated than that since there is no concept of a queue in Prefect, you can think of a work queue more as a filter for the agent to decide which work to pick up, but once the agent did pick up some work and started running it on some remote infra deployed by the flow runner, it's not as simple to kill it since Prefect doesn't have access to your infrastructure and can only remotely initialize some action via an API call
Tim Helfensdörfer
05/31/2022, 9:53 AMAnna Geller
05/31/2022, 10:00 AMwhich are not queuesthey are still queues, what I meant is that a mental model of a "filter" makes more sense to understand the inner workings here because a queue can make you think Prefect uses some RabbitMQ, SQS or similar system here, while (to keep Orion lightweight and with a minimal set of dependencies), it uses only backend DB and API for that purpose -- but it works the same way as a queue would
Tim Helfensdörfer
05/31/2022, 10:03 AM