dosubot[bot] commented on issue #36294: URL: https://github.com/apache/superset/issues/36294#issuecomment-3582066016
<!-- Greeting --> Hi @Umbrella-zero! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> Superset 5.0.0 does not officially support Redis Cluster as a Celery broker or result backend. All documentation and code examples use standalone Redis, and there are no references to Redis Cluster support or configuration in the codebase or docs. This limitation is also confirmed by maintainers and in user discussions—only standalone Redis (and, with recent changes, Redis Sentinel) is supported for async queries and reports, not Redis Cluster. There are no known workarounds or configuration patterns that enable Redis Cluster support for Celery in Superset 5.0.0; all successful setups use standalone Redis or RabbitMQ as the broker and backend [[source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/configuration/async-queries-celery.mdx)][[source](https://github.com/apache/superset/issues/31842)]. Errors like "Failed to start remote query on a worker" and broken scheduled reports are often caused by missing or misconfigured RESULTS_BACKEND or GLOBAL_ASYNC_QUERIES_CACHE_BACKEND, but even with correct config, Redis Cluster is not supported and will not work reliably [[source](https://github.com/apache/superset/discussions/34382)][[source](https://github.com/apache/superset/discussions/34650)]. If you need high availability, consider using Redis Sentinel (which is partially supported) or RabbitMQ. For now, the only robust solution is to use a standalone Redis instance for Celery and async features in Superset 5.0.0. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/197a43f1-0549-4922-a1a4-9ec1582b387f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/197a43f1-0549-4922-a1a4-9ec1582b387f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/197a43f1-0549-4922-a1a4-9ec1582b387f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/197a43f1-0549-4922-a1a4-9ec1582b387f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/197a43f1-0549-4922-a1a4-9ec1582b387f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/197a43f1-0549-4922-a1a4-9ec1582b387f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/197a43f1-0549-4922-a1a4-9ec1582b387f?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Superset%205.0.0%20does%20not%20officially%20support%20Redis%20Cluster%20as%20a%20Celery%20broker%20or%20result%20backend.%20All%20documentation%20and%20code%20examples%20use%20standalone%20Redis%2C%20and%20there%20are%20no%20references%20to%20Redis%20Cluster%20support%20or%20configuration%20in%20the%20codebase%20or%20docs.%20This%20limitation%20is%20also%20confirmed%20by%20maintainers%20and%20in%20user%20discussions%E2%80%94only%20standalone%20Redis%20%28and%2C%20with%20recent%20changes%2C%20Redis%20Sentinel%29%20is%20supported%20for%20async%20queries%20and%20reports%2C%20not%20Redis%20Cluster.%20There%20are%20no%20known%20workarounds%20or%20configuration%20patterns%20that%20enable%20Redis%20Cluster%20support%20for%20Celery%20in%20Superset%205.0.0 %3B%20all%20successful%20setups%20use%20standalone%20Redis%20or%20RabbitMQ%20as%20the%20broker%20and%20backend%20%5B%5Bsource%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/configuration/async-queries-celery.mdx%29%5D%5B%5Bsource%5D%28https%3A//github.com/apache/superset/issues/31842%29%5D.%0A%0AErrors%20like%20%22Failed%20to%20start%20remote%20query%20on%20a%20worker%22%20and%20broken%20scheduled%20reports%20are%20often%20caused%20by%20missing%20or%20misconfigured%20RESULTS_BACKEND%20or%20GLOBAL_ASYNC_QUERIES_CACHE_BACKEND%2C%20but%20even%20with%20correct%20config%2C%20Redis%20Cluster%20is%20not%20supported%20and%20will%20not%20work%20reliably%20%5B%5Bsource%5D%28https%3A//github.com/apache/superset/discussions/34382%29%5D%5B%5Bsource%5D%28https%3A//github.com/apache/superset/discussions/34650%29%5D.%0A%0AIf%20you%20need%20high%20availability%2C%20consider%20using%20Redis%20Sentinel%20%28which%20is%20partially%20supported%29%20or%2 0RabbitMQ.%20For%20now%2C%20the%20only%20robust%20solution%20is%20to%20use%20a%20standalone%20Redis%20instance%20for%20Celery%20and%20async%20features%20in%20Superset%205.0.0.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/36294) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
