Hi everyone, If a pipeline is in running state, do...
# ask-community
n
Hi everyone, If a pipeline is in running state, does repository server shut down if we manually try to shutdown the repository via the graphql api? If yes, what happens to the pipeline? does it terminate?
r
The job runs autonomously once its been launched - it doesn’t need to communicate back to the repository server.
n
Not sure if I understand it correctly, but this is what I understood: Since, I am not using k8s-run-launcher, repository server and pipeline execution must be in the same pod. If shutdown mutation shuts down the pod, how can pipeline continue to execute?
r
Ah yeah, in that case, if you’re using the
DefaultRunLauncher
, your run is executed as a subprocess in your gRPC repository server. If that server gets shutdown, there will be undefined behavior for your existing runs
We have a Run Monitoring abstraction that takes care of this, https://docs.dagster.io/deployment/run-monitoring#run-monitoring, but it’s not implemented for the
DefaultRunLauncher
yet.
n
Thanks for to the help. Will look into docs.