Is 'rpc://' a valid value for the 'celery_result_backend' setting in airflow config? It doesn't seem to work.
'rpc://'是airflow配置中'celery_result_backend'设置的有效值吗?它似乎不起作用。
Assumed it works, as its a valid value in core celery config.
假设它有效,因为它是核心芹菜配置中的有效值。
1 个解决方案
#1
0
Since we're using Celery on Redis the URLs both start with: redis://.
由于我们在Redis上使用Celery,因此URL均以:redis://开头。
If you were using Celery with RabbitMQ the URLs would start with: amqp://
如果你在使用带有RabbitMQ的Celery,URL将从以下开始:amqp://
The AWS SQS ones would start with: sqs://
AWS SQS将以:sqs://开头
I don't see any queue broker url that starts with rpc:// in the broker documentation.
我没有在代理文档中看到任何以rpc://开头的队列代理URL。
I do see that the results backend for RabbitMQ could start with rpc:// Since it's just a string passed to the library in question did you install with celery[librabbitmq] and you're not mixing up the two like I almost did?
我确实看到RabbitMQ的结果后端可以从rpc开始://因为它只是一个字符串传递给有问题的库你用celery [librabbitmq]安装并且你不是像我差不多那样把它们混在一起吗?
#1
0
Since we're using Celery on Redis the URLs both start with: redis://.
由于我们在Redis上使用Celery,因此URL均以:redis://开头。
If you were using Celery with RabbitMQ the URLs would start with: amqp://
如果你在使用带有RabbitMQ的Celery,URL将从以下开始:amqp://
The AWS SQS ones would start with: sqs://
AWS SQS将以:sqs://开头
I don't see any queue broker url that starts with rpc:// in the broker documentation.
我没有在代理文档中看到任何以rpc://开头的队列代理URL。
I do see that the results backend for RabbitMQ could start with rpc:// Since it's just a string passed to the library in question did you install with celery[librabbitmq] and you're not mixing up the two like I almost did?
我确实看到RabbitMQ的结果后端可以从rpc开始://因为它只是一个字符串传递给有问题的库你用celery [librabbitmq]安装并且你不是像我差不多那样把它们混在一起吗?