Hi Team! Using dagster V0.12.14 with user-code-dep...
# ask-community
Hi Team! Using dagster V0.12.14 with user-code-deployment helm chart. Triggered a pipeline & it's not able to complete this run because of below error. what should be the cause and how we can handle it ? appreciate the helps. Thanks.
Copy code
dagster.core.errors.DagsterLaunchFailedError: Tried to start a run on a server after telling it to shut down

  File "/usr/local/lib/python3.7/site-packages/dagster/core/instance/__init__.py", line 1386, in submit_run
    SubmitRunContext(run, workspace=workspace)
  File "/usr/local/lib/python3.7/site-packages/dagster/core/run_coordinator/default_run_coordinator.py", line 32, in submit_run
    self._instance.launch_run(pipeline_run.run_id, context.workspace)
  File "/usr/local/lib/python3.7/site-packages/dagster/core/instance/__init__.py", line 1450, in launch_run
    self._run_launcher.launch_run(LaunchRunContext(pipeline_run=run, workspace=workspace))
  File "/usr/local/lib/python3.7/site-packages/dagster/core/launcher/default_run_launcher.py", line 105, in launch_run
    res.message, serializable_error_info=res.serializable_error_info
Hi Mohammed - unfortunately the best advice i can give you is to consider using the K8sRunLauncher instead of the DefaultRunLauncher so that you have full isolation between the user code servers and your launched runs (with each run happening in its own k8s pod). These types of errors stem from the fact that the same pod is both serving your code and being used to launch runs
Agree, but is it possible to handle this error without K8sRunLauncher.
I'm not sure of a way to ensure that unfortunately other than changing run launchers
Okay Thank You @daniel.