redis.clients.jedis.exceptions.JedisException: Can connect to sentinel, but MasterServerName:6381 seems to be not monitored...

Hot problem!
This exception has a lot of traffic. You can help 15 users by writing a short tip.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by gauthamgshet
, 1 year ago
Can connect to sentinel, but MasterServerName:6381 seems to be not monitored...
via Stack Overflow by gary
, 1 year ago
Can connect to sentinel, but 127.0.0.1:26379 seems to be not monitored...
redis.clients.jedis.exceptions.JedisException: Can connect to sentinel, but MasterServerName:6381 seems to be not monitored...
at redis.clients.jedis.JedisSentinelPool.initSentinels(JedisSentinelPool.java:176)
at redis.clients.jedis.JedisSentinelPool.(JedisSentinelPool.java:94)
at redis.clients.jedis.JedisSentinelPool.(JedisSentinelPool.java:81)
at redis.clients.jedis.JedisSentinelPool.(JedisSentinelPool.java:69)
at redis.clients.jedis.JedisSentinelPool.(JedisSentinelPool.java:44)
at jedisJmeterTest.RedisServerConnFailoverTest.main(RedisServerConnFailoverTest.java:35)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago

Know the solutions? Share your knowledge to help other developers to debug faster.