Hello, guys
When someone use jedis 2.9.4 connect to redis sentinel(version 4.0.14), It's ok.
After redis sentinel update to 5.0.10, May be some failed would happen like follow.
Cannot get master address from sentinel running @
192.168.72.129:26379.
Reason: redis.clients.jedis.exceptions.JedisConnectionException:
Failed connecting to host
192.168.72.129:26379. Trying next one.
redis.clients.jedis.exceptions.JedisConnectionException:
All sentinels down, cannot determine where is mymaster master is running...
The reason is that redis sentinel's auth.
We know that redis sentinel add auth in version 5.0.1
But user may not know, he/she will try to update jedis's version to newest.
Through the sentinel's auth has been fix in
#2154 #2077, but user may not pass sentinel's password because the origin code not do it.
Could add more prompt to help users when they fail to connect with sentinel?
A warn log when they not setup sentinel's password.
I have been consum 2 days for find why I cannot conntect to sentinel(when redis version from 4.0.14 to 5.0.10), maybe others will meet trouble same as mine.