Hi, is there any way to make dagit more verbose? I...
# announcements
f
Hi, is there any way to make dagit more verbose? I think it's ignoring the
run_launcher
section in my
dagster.yaml
but I don't see any error or anything...
a
you can click the “instance details” button in the top left to see what its using
f
I found the issue, it was a missing dependency (dagster-k8s actually) but it didn't complain at all and simply used the default run_launcher
I have got now Dagit properly launching jobs from my machine, so that's good news, still the configuration that is loading is incorrect. I need to tidy up my docker-compose and terraform files 😓
If I'm not wrong, it seems that I need at least 2 different
dagster.yaml
, one for the Dagit instance (with k8s run launcher, etc.) and one specifically for the k8s jobs.
Another thing that I have noticed is that, in my case for example I have 3 solids without inter-dependencies and Dagit is launching 3 jobs, one per solid... I was expecting it to launch only 1 job and run all the solids there using in proc
Is it possible to achieve this behaviour?
a
If you use
K8sRunLauncher
and don’t set the
execution:
section of run config it should default to
in_process
the k8s jobs should able to use the same
dagster.yaml
as
dagit