19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
dagster-de
dagster-cube
gigs-freelance
dagster-wandb
dagster-machine-learning
dagster-bigquery
tools
dagster-dask
dagster-snowflake
dagster-releases
data-platform-design
events
dagster-serverless
dagster-noteable
introductions
dagster-airflow
dagster-cloud
random
dagster-dbt
faq-read-me-before-posting
dagster-airbyte
dagster-spatial
dagster-support
announcements
github-discussions
豆瓣酱帮
dagster-feedback
dagstereo
dagster-ecs
dagster-kubernetes
jobs
dagster-showcase
Title
t
Tobias Pankrath
03/03/2023, 2:53 PMIs there a way to stop the execution of new runs? I have a Q of 2000 and I want the currently running to finish and no new ones to start
Also: killing a dagster instance started with
dagster devd
daniel
03/03/2023, 3:56 PMHey Tobias - which processes are getting left over, and what operating system are you running
dagster devWe don't currently have a way to stop new runs from being enqueued (other than turning off any schedules and sensors that are launching runs, which can be done from the Dagster UI)
t
Tobias Pankrath
03/03/2023, 5:39 PMHi Daniel, it's a linux (ubuntu 20.04). I don't know which exactly, but they are executing runs.
Stopping from being enqueued is not needed, stopping from being run would be good. Or have an easy way to clean up the Q.
d
daniel
03/03/2023, 5:40 PMdo you have the name of the command that the hanging processes are running? (Maybe
dagster api grpcDo the processes clean themselves up once the run that they're executing is finished?
t
Tobias Pankrath
03/06/2023, 7:39 AMsry for the late response
its dagster api grpc. If I quit the main process, it will terminate and leave several processes left over. some of them are runs that finish and quit afterwards and ~6 or so are left over, one of them being dagster dev grpc, I already have
pgrep -alf dagsteruntil thursday