Cannot init a connected sentinel

redis.clients.jedis.exceptions.JedisException
at redis.clients.jedis.JedisSentinelPool.initSentinels
at redis.clients.jedis.JedisSentinelPool.<init>
at redis.clients.jedis.JedisSentinelPool.<init>

Matching stack traces (2)

  1. gauthamgshetvia GitHub1 year ago
    Can connect to sentinel, but MasterServerName:6381 seems to be not monitored...
  2. Can connect to sentinel, but 127.0.0.1:26379 seems to be not monitored...

See Also

Children

  • 1 web pages  - JedisSentinelPool.<init>() has thrown a JedisException
    redis.clients.jedis.exceptions.JedisException
        at redis.clients.jedis.JedisSentinelPool.initSentinels()
        at redis.clients.jedis.JedisSentinelPool.<init>()
        at redis.clients.jedis.JedisSentinelPool.<init>()
        at redis.clients.jedis.JedisSentinelPool.<init>()
        at redis.clients.jedis.JedisSentinelPool.<init>()

Typical exception messages

  1. 1 crashes - Can connect to sentinel, but 172.16.8.222 seems to be not monitored...
  2. 1 crashes - Can connect to sentinel, but 127.0.0.1:26379 seems to be not monitored...
  3. 1 crashes - Can connect to sentinel, but MasterServerName:6381 seems to be not monitored...