feat: connect to redis sentinel for redis queue (backport #25506) #25557
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use redis sentinel for redis queue connection.
It is setup for production only.
Uses extra keys from common_site_config.json
At the moment we can connect to single redis master for queue. With this we can connect to sentinel cluster.
https://redis.io/docs/management/sentinel
To try it with frappe_docker/devcontainer make following changes to .devcontainer/docker-compose.yml
add redis_cache_* keys to common_site_config.json
Note: Nothing has changed to the
redis_queue
key. It will be used by socketio.Docs: https://frappeframework.com/app/wiki-page-patch/372939da4e
This is an automatic backport of pull request #25506 done by [Mergify](https://mergify.com).