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

GitHub | gauthamgshet | 11 months ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    JedisSentinelPool unable to detect the Redis master

    GitHub | 11 months ago | gauthamgshet
    redis.clients.jedis.exceptions.JedisException: Can connect to sentinel, but MasterServerName:6381 seems to be not monitored...
  2. 0

    Spring XD distributed mode Redis Sentinel

    Stack Overflow | 1 year ago | gary
    redis.clients.jedis.exceptions.JedisException: Can connect to sentinel, but 127.0.0.1:26379 seems to be not monitored...

    1 unregistered visitors

    Root Cause Analysis

    1. redis.clients.jedis.exceptions.JedisException

      Can connect to sentinel, but MasterServerName:6381 seems to be not monitored...

      at redis.clients.jedis.JedisSentinelPool.initSentinels()
    2. Jedis
      JedisSentinelPool.<init>
      1. redis.clients.jedis.JedisSentinelPool.initSentinels(JedisSentinelPool.java:176)
      2. redis.clients.jedis.JedisSentinelPool.<init>(JedisSentinelPool.java:94)
      3. redis.clients.jedis.JedisSentinelPool.<init>(JedisSentinelPool.java:81)
      4. redis.clients.jedis.JedisSentinelPool.<init>(JedisSentinelPool.java:69)
      5. redis.clients.jedis.JedisSentinelPool.<init>(JedisSentinelPool.java:44)
      5 frames
    3. jedisJmeterTest
      RedisServerConnFailoverTest.main
      1. jedisJmeterTest.RedisServerConnFailoverTest.main(RedisServerConnFailoverTest.java:35)
      1 frame