There actually isn’t a celery run launcher – you’r...
# announcements
s
There actually isn’t a celery run launcher – you’re probably looking for the celery executor. More info here about executing on celery here: https://docs.dagster.io/deploying/celery. An explanation of run launchers and executors here: https://docs.dagster.io/overview/run-launchers-executors/run-launcher. More info about the instance and configuring run launchers here: https://docs.dagster.io/overview/instances/dagster-instance#instance-configuration-yaml
s
oh Noah is doing his own fancy run launcher
in order to hack together solids executing in their own containers
i’m looking forward to seeing the wizardry 🙂
s
ah my bad, that’s exciting!
n
This is more for avoiding overload on the dagit container
Since I don't want launching 100 pipelines to fork off 100 copies of the CLI 🙂
Would quickly hit the container resource limit and fall over
s
ah we will have built in support for this in Dagster in our 0.10.0 release cc @johann
more specifically the queueing part, not the solids executing in their own containers part
n
Local queuing will be great out of the box, but cramming it in a rabbit queue means I can autoscale the runner containers too 🙂
Elastic all the things all the things