https://dagster.io/ logo
Title
j

Josh Lloyd

06/25/2021, 6:02 PM
Is there a way to stop or restart the grpc server? Once the container with the run worker is up and I can see my pipelines in Dagit I tried running
dagster api grpc -h 0.0.0.0 -p 4000 --python-file dagster_repos.py
but that just causes Dagit confusion that causes it to constantly switch between the new pipeline file and the old one. Seems like I need to stop the first grpc process first.
d

daniel

06/25/2021, 6:22 PM
Hi Josh - how did you originally start the server?
j

Josh Lloyd

06/25/2021, 6:23 PM
Oh sorry, should have mentioned I currently have this all running from a docker-compose configuration so the original
dagster api grpc
command is the
CMD
in the dockerfile for the container being discussed
Maybe I should also state that my actual end goal is to refresh the pipelines. I have the container attached to my repo/pipeline code through a volume. So when I update the code, I’d like it to update in Dagit without rebuilding the image.
d

daniel

06/25/2021, 6:43 PM
Got it - our best answer for this at the moment is to restart the container via "docker-compose restart <service name>".
j

Josh Lloyd

06/25/2021, 6:44 PM
ah, that’s painless enough. I’ll go with that. Thanks a bunch!
d

daniel

06/25/2021, 6:45 PM
np! We also just added a new graphql call in the release that went out yesterday that lets you shut down the server via graphql, and it's possible to set up your docker-compose so that your server automatically restarts when it's shut down - but that call isn't exposed in the dagit UI quite yet
j

Josh Lloyd

06/25/2021, 6:55 PM
oh, very nice!! I’ll take a look at that then