GitHub user dosubot[bot] added a comment to the discussion: Superset → PostgreSQL: recurring SSL EOF and connection reset logs
<!-- Answer --> Yes, that warning means a Celery worker process is running in your environment. In the Superset Helm chart, the Celery worker pod is enabled by default unless you explicitly disable it in your values.yaml. This explains why you see both the deprecation warning and recurring PostgreSQL connection resets: the Celery worker is making and closing connections to your metadata database, not the warning itself. If you don't want any Celery components running, set `supersetWorker.replicas.enabled: false` in your Helm values and redeploy. If you do need Celery, you can address the warning by adding `broker_connection_retry_on_startup = True` to your `CeleryConfig` in `superset_config.py` ([example](https://github.com/apache/superset/discussions/34943)). <!-- 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/9c955461-eafa-46a0-8e7c-b2603defd570?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9c955461-eafa-46a0-8e7c-b2603defd570?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9c955461-eafa-46a0-8e7c-b2603defd570?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9c955461-eafa-46a0-8e7c-b2603defd570?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9c955461-eafa-46a0-8e7c-b2603defd570?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9c955461-eafa-46a0-8e7c-b2603defd570?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9c955461-eafa-46a0-8e7c-b2603defd570?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Yes%2C%20that%20warning%20means%20a%20Celery%20worker%20process%20is%20running%20in%20your%20environment.%20In%20the%20Superset%20Helm%20chart%2C%20the%20Celery%20worker%20pod%20is%20enabled%20by%20default%20unless%20you%20explicitly%20disable%20it%20in%20your%20values.yaml.%20This%20explains%20why%20you%20see%20both%20the%20deprecation%20warning%20and%20recurring%20PostgreSQL%20connection%20resets%3A%20the%20Celery%20worker%20is%20making%20and%20closing%20connections%20to%20your%20metadata%20database%2C%20not%20the%20warning%20itself.%0A%0AIf%20you%20don%27t%20want%20any%20Celery%20components%20running%2C%20set%20%60supersetWorker.replicas.enabled%3A%20false%60%20in%20your%20Helm%20values%20and%20redeploy.%20If%20you%20do%20need%20Celery%2C%20you%20c an%20address%20the%20warning%20by%20adding%20%60broker_connection_retry_on_startup%20%3D%20True%60%20to%20your%20%60CeleryConfig%60%20in%20%60superset_config.py%60%C2%A0%28%5Bexample%5D%28https%3A//github.com/apache/superset/discussions/34943%29%29.) [](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/36420) GitHub link: https://github.com/apache/superset/discussions/36420#discussioncomment-15171278 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
