The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Screenshot from 2022-03-04 23-40-44.png

Hi, All.
What is mean, when run is in `Started` status, but in the same time all tasks have already finished?

Hi Alexander, could you give a few more details? Is the run still stuck in `Started` ?

Hi <@U015C9U9RLK>
I am trying to build simple pipeline with using `celery_k8s` executor. Here you can find whole project <https://github.com/habibutsu/dagster-research> based on minikube as playground for kubernetes.

I noticed some strange thing, when I run job with configuration
```ops:
  init_step:
    inputs:
      amount: 5```
everything works fine, but if increase parameter `amount` to 20 or more despite all tasks complete successfully , run stay in status `started`

Hi <@URZU5ADB9>, sorry just getting to this now. It looks like your helm values don’t configure the CeleryK8sRunLauncher, which is a requirement for using the `celery_k8s_job_executor`

That’s configured here <https://github.com/dagster-io/dagster/blob/master/helm/dagster/values.yaml#L386>

If that doesn’t help, it would useful to have the logs from the `dagster-run-&lt;run_id&gt;` K8s job

Isn't this configuration enough?
<https://github.com/habibutsu/dagster-research/blob/master/values/dagster.yaml#L3>