Channels
dagster-de
topic-async-execution
dagster-jp
dagster-cube
gigs-freelance
dagster-wandb
dagster-feedback
dagster-machine-learning
dagster-bigquery
dagster-support
dagster-dask
dagster-snowflake
dagster-releases
dagster-dbt
faq-read-me-before-posting
tools
dagster-ext
project-flexible-range-backfills
data-platform-design
events
dagster-serverless
dagster-noteable
introductions
dagster-airflow
dagster-cloud
random
dagster-airbyte
dagster-spatial
announcements
github-discussions
豆瓣酱帮
dagstereo
dagster-ecs
dagster-kubernetes
jobs
dagster-showcase
data-quality-asset-checks
Powered by
#announcements
Title
s
sashank
10/27/2020, 10:38 PM
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
schrockn
10/27/2020, 10:38 PM
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
sashank
10/27/2020, 10:39 PM
ah my bad, that’s exciting!
n
Noah K
10/27/2020, 10:39 PM
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
sashank
10/27/2020, 10:47 PM
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
Noah K
10/27/2020, 10:49 PM
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
5 Views
Post