GitHub user dosubot[bot] added a comment to the discussion: Async Queries redis connection error
<!-- Greeting --> Hi @MorieeLM! I'm [Dosu](https://go.dosu.dev/dosubot) and Iām helping the superset team. <!-- Answer --> Your error happens because Superset is trying to connect to Redis at localhost:6379, but in Kubernetes, Redis usually runs in its own pod and should be accessed via its service name, not localhost. This causes connection refused errors unless Redis is running in the same container, which is not typical for Kubernetes setups. The UI hangs with "waiting for postgresql" because async queries and Celery workers can't connect to Redis, so queries never complete and results aren't cached or returned. To fix this, make sure your REDIS_HOST environment variable is set to your Redis service name (for example, superset-redis-master or superset-redis-headless), not localhost. You can check the current value by running kubectl exec on a Superset pod and running env | grep REDIS. Update your Helm values.yaml or Kubernetes manifests to set REDIS_HOST using extraEnv or extraSecretEnv, and reference it in your configOverrides. For example: ```yaml extraEnv: REDIS_HOST: superset-redis-master REDIS_PORT: "6379" REDIS_DB: "0" REDIS_CELERY_DB: "1" ``` Then, in your configOverrides, use os.environ.get("REDIS_HOST") and similar for all Redis-related config. After updating, redeploy Superset and the workers so the new settings take effect. If Redis requires authentication, include the username and password in your Redis URLs. References: - [Kubernetes Redis config best practices](https://github.com/apache/superset/issues/32558) - [Superset async queries and Celery config](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/installation/kubernetes.mdx) - [How async queries use Redis config](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/async_events/async_query_manager.py) <!-- 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/64d5f698-9129-4c07-8b08-8ebd9b67fbfe?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/64d5f698-9129-4c07-8b08-8ebd9b67fbfe?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/64d5f698-9129-4c07-8b08-8ebd9b67fbfe?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/64d5f698-9129-4c07-8b08-8ebd9b67fbfe?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/64d5f698-9129-4c07-8b08-8ebd9b67fbfe?feedback_type=hallucination) | [Report š](https://app.dosu.dev/response-feedback/64d5f698-9129-4c07-8b08-8ebd9b67fbfe?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/64d5f698-9129-4c07-8b08-8ebd9b67fbfe?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)& nbsp;[](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/discussions/34650) GitHub link: https://github.com/apache/superset/discussions/34650#discussioncomment-14080157 ---- This is an automatically sent email for notifications@superset.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@superset.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
