dosubot[bot] commented on issue #33604: URL: https://github.com/apache/superset/issues/33604#issuecomment-2916243722
<!-- Answer --> Your configuration for Redis Sentinel in Superset is mostly correct: you should set CACHE_TYPE to RedisSentinelCache and provide the sentinel servers and master name. This is supported in recent Superset versions for dataset caching and async queries ([source](https://github.com/apache/superset/blob/master/UPDATING.md)). A few things to check: 1. Make sure your CUSTOM_SENTINEL_SERVERS list contains the actual hostnames or IPs of your Sentinel nodes, not just the string "dns". For example: ```python CUSTOM_SENTINEL_SERVERS = [ ("sentinel1.example.com", 26379), ("sentinel2.example.com", 26379), ("sentinel3.example.com", 26379) ] ``` 2. Ensure CACHE_REDIS_SENTINEL_MASTER_NAME is set to the correct Redis master name as configured in your Sentinel setup (it should be a string, e.g., "mymaster"). 3. If your Redis or Sentinel requires authentication, you may need to include password fields in your config. The RedisSentinelCacheBackend class supports parameters like password and sentinel_password ([source](https://github.com/apache/superset/blob/master/superset/async_events/cache_backend.py)). 4. If you are using SSL, make sure to set the appropriate SSL parameters. The backend handles SSL options, but Sentinel itself does not support SSL directly; SSL is only used between Superset and the Redis master. 5. If you still cannot connect, check the Superset logs for any error messages—they often provide clues about misconfiguration or network issues. 6. Verify network connectivity from your Superset instance to all Sentinel nodes and that the master name matches what Sentinel expects. If you can share the specific error message from your logs, I can help troubleshoot further. <!-- Dosu Comment Footer --> *To reply, just mention my name [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/177efd4b-4920-4de2-976c-dfd3338cf904?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/177efd4b-4920-4de2-976c-dfd3338cf904?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/177efd4b-4920-4de2-976c-dfd3338cf904?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/177efd4b-4920-4de2-976c-dfd3338cf904?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/177efd4b-4920-4de2-976c-dfd3338cf904?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/177efd4b-4920-4de2-976c-dfd3338cf904?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/177efd4b-4920-4de2-976c-dfd3338cf904?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [! [Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/33604) -- 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]
