REDIS_SENTINEL_NODES

[ghost]

How do I configure Superset to point at a sentinel Redis node so that it can automatically connect to Redis Master?

[dosubot[bot]]

To configure Superset to point at a sentinel Redis node for automatic connection to the Redis Master, you need to use the RedisSentinelCacheBackend class in your Superset configuration file. Here's an example configuration:

# Superset configuration file

# Define the list of sentinel nodes
CACHE_REDIS_SENTINELS = [("sentinel1.example.com", 26379), ("sentinel2.example.com", 26379)]

# Define the name of the master node
CACHE_REDIS_SENTINEL_MASTER = "mymaster"

# Optional: Redis password
CACHE_REDIS_PASSWORD = "your_redis_password"

# Optional: Sentinel password
CACHE_REDIS_SENTINEL_PASSWORD = "your_sentinel_password"

# Optional: Database number
CACHE_REDIS_DB = 0

# Optional: Key prefix
CACHE_KEY_PREFIX = "superset_"

# Optional: SSL configuration
CACHE_REDIS_SSL = False
CACHE_REDIS_SSL_CERTFILE = None
CACHE_REDIS_SSL_KEYFILE = None
CACHE_REDIS_SSL_CERT_REQS = "required"
CACHE_REDIS_SSL_CA_CERTS = None

Adjust the parameters as needed for your specific environment to enable Superset to connect to the Redis master node automatically using the specified sentinel nodes ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[ghost]

@dosu
I am doing deployment using helm chart, please suggest in it.

[dosubot[bot]]

To configure Redis Sentinel in a Superset deployment using the Helm chart, you would typically need to customize the values.yaml file. However, the current Superset Helm chart documentation does not provide specific instructions or examples for integrating with Redis Sentinel.

You can start by disabling the default Redis setup in the Helm chart and specifying your external Redis Sentinel configuration. Here’s a general approach you might consider:

1. Disable the default Redis setup: Set redis.enabled to false in your values.yaml file to disable the default Redis instance provided by the Helm chart.

2. Specify external Redis Sentinel configuration: You will need to manually configure the connection to your Redis Sentinel setup. This might involve setting environment variables or modifying the Superset configuration to use the RedisSentinelCacheBackend class, as described in the previous response.

Unfortunately, without specific support for Redis Sentinel in the Helm chart, you may need to handle some of the configuration manually or extend the chart to support your needs.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}