Redis Sentinel configuration issue in common_site_config.json

Frappe Framework
, ,
1

Why is the redis_cache variable still necessary even though the redis_queue_sentinels variable already exists ?

This is my example config

{
 "redis_cache": "redis://redis-sentinel-node-0.redis-sentinel-headless.default.svc.cluster.local:6379",
 "redis_cache_master_service": "mymaster",
 "redis_cache_sentinel_enabled": 1,
 "redis_cache_sentinels": [
  "redis-sentinel:26379"
 ],
 "redis_queue": "redis://redis-sentinel-node-0.redis-sentinel-headless.default.svc.cluster.local",
 "redis_queue_master_service": "mymaster",
 "redis_queue_sentinel_enabled": 1,
 "redis_queue_sentinels": [
  "redis-sentinel:26379"
 ]
}

If I don’t define the redis_cache variable, commands like bench migrate won’t work.

2

It’s not necessary. Whatever value it has will be ignored as long as redis_cache_sentinel_enabled is set.

3

I noticed that when I run bench-related commands, such as bench migrate, it uses the redis_cache variable. If it’s not set, I can’t run bench migrate commands.

4

Ideally builds and deployments are different.

Bench assumes you’ve a vm and redis is always connected.

Crashing frontend - #2 by revant_one check this how it needs redis cache during builds.

Even frappe/press assumes everyone will get a localhost redis always connected.