redis sentinel default configuration broken
See original GitHub issueUsing springBoot with version 2.0.0.M6 and redis.clients:jedis:2.9.0,with config:
spring:
redis:
sentinel:
nodes: 0.0.0.0:26379,0.0.0.0:26479,0.0.0.0:26579
master: mymaster
But Spring Boot not use sentinel config,but resolve to localhost:6379.By debugging I found the above code is the cause: If the pool configuration is leave out,Spring Boot will resolve to localhost:6379
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
High availability with Redis Sentinel
Sentinel will simply refuse to start if no configuration file is given or if the configuration file path is not writable. Sentinels by...
Read more >Redis Sentinel Configuration not working - Stack Overflow
I am trying to set up sentinel using two redis nodes. Please find inline the conf file. Can someone help me to fix...
Read more >Redis Sentinel Configuration - UiPath Documentation Portal
To start Redis in Sentinel mode, run redis-server /etc/redis/sentinel.conf –sentinel . Sentinel for Redis Server on Windows. After installing Redis server ...
Read more >Troubleshooting Redis - GitLab Docs
If you get an error like: Redis::CannotConnectError: No sentinels available. , there may be something wrong with your configuration files or it can...
Read more >Redis Sentinel | Creatio Academy
Configure Creatio to work with Redis Sentinel ... If the Redis Master instance is not working correctly, Sentinel promotes one ... By default,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Nothing scheduled yet. Releasing Kay SR4 would make sense right before Spring Boot RC2.
The issue is fixed in Spring Data Redis entirely.
It looks like this has been fixed entirely on the Data Redis side of things. We’ll pick this up in the next Spring Data Kay service release. @mp911de do you have any plans for SR4 at the moment?