Replies: 1 comment
-
Hi My problem was that I didn't configure broker/backend for the celery_executor I had a broker rabbitmq pyamqp://dagster:dagster@broker:5672/dagster-broker with user:dagster, password dagster and vhost: dagster-broker The problem was that I had no configuration of broker/backend for the celery client that is celery_executor Finally I make it work by adding celery_executor configuration directly in definition:
Now my question is: is there another way to configure celery_executor by config file or env variable to avoid configuring it each time/job à want to use celery_executor ? |
Beta Was this translation helpful? Give feedback.
-
Hello
I'm trying to execute a task on celery executor on the Open Source Dagster self hosted
I have to admit that the documentation is not really exhaustive so maybe I'm missing something
So this is docker compose stack. When up all container start correctly without error
celery container seems to be well initialized and connected to broker
But when I click on "materialize" on my job "all_assets" in the job list in Dagster Ui I get this following error
I don't see where it is coming from. I tried with default celery backend and postgresql backend it is the same...
I'm surely missing something as I'm not so familiar with celery too for the moment
If you have an idea of the solution it could be great
Thank you in advance
Here the error when I click "materialize" my job:
here you'll find my configurations. I think all needed files are here but don't hesitate to ask me more information if needed
Beta Was this translation helpful? Give feedback.
All reactions