[ 
https://issues.apache.org/jira/browse/NIFI-9019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eduardo Mota Fontes reassigned NIFI-9019:
-----------------------------------------

    External issue URL: 
https://docs.spring.io/spring-data/redis/docs/current/changelog.txt
         Fix Version/s: 1.15.0
              Assignee: Eduardo Mota Fontes

There is a bug in Spring + Jedis. Fixed by "[*NIFI-8948*] Upgrade Spring 
Framework to 5.3.9 and Spring Security to 5.5.1"

> Redis Sentinel Database index > 0 connections error in v. 1.14.0
> ----------------------------------------------------------------
>
>                 Key: NIFI-9019
>                 URL: https://issues.apache.org/jira/browse/NIFI-9019
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.14.0
>            Reporter: Jens M Kofoed
>            Assignee: Eduardo Mota Fontes
>            Priority: Major
>             Fix For: 1.15.0
>
>
> After upgrading from v. 1.13.2 to v. 1.14.0 I have issues with Redis 
> connetions
> I seems if a RedisConnectionPoolService is configured with a Database Index = 
> 0 there are no issues.
> But if I have the Database Index set to 3 I got the following errors in the 
> log:
> 2021-08-06 11:18:21,123 INFO [Timer-Driven Process Thread-13] 
> o.a.n.r.s.RedisConnectionPoolService 
> RedisConnectionPoolService[id=160a1056-017b-1000-0000-00005533ce4b] 
> Connecting to Redis in sentinel mode...
> 2021-08-06 11:18:21,123 INFO [Timer-Driven Process Thread-13] 
> o.a.n.r.s.RedisConnectionPoolService 
> RedisConnectionPoolService[id=160a1056-017b-1000-0000-00005533ce4b] Redis 
> master = mymaster
> 2021-08-06 11:18:21,123 INFO [Timer-Driven Process Thread-13] 
> o.a.n.r.s.RedisConnectionPoolService 
> RedisConnectionPoolService[id=160a1056-017b-1000-0000-00005533ce4b] Redis 
> sentinel at redis-01:26379
> 2021-08-06 11:18:21,123 INFO [Timer-Driven Process Thread-13] 
> o.a.n.r.s.RedisConnectionPoolService 
> RedisConnectionPoolService[id=160a1056-017b-1000-0000-00005533ce4b] Redis 
> sentinel at redis-02:26379
> 2021-08-06 11:18:21,123 INFO [Timer-Driven Process Thread-13] 
> o.a.n.r.s.RedisConnectionPoolService 
> RedisConnectionPoolService[id=160a1056-017b-1000-0000-00005533ce4b] Redis 
> sentinel at redis-03:26379
> 2021-08-06 11:18:21,124 INFO [Timer-Driven Process Thread-13] 
> redis.clients.jedis.JedisSentinelPool Trying to find master from available 
> Sentinels...
> 2021-08-06 11:18:21,124 DEBUG [Timer-Driven Process Thread-13] 
> redis.clients.jedis.JedisSentinelPool Connecting to Sentinel redis-01:26379
> 2021-08-06 11:18:21,124 WARN [NiFi Web Server-4964] 
> org.apache.nifi.audit.ProcessorAuditor Unable to record actions: null
> 2021-08-06 11:18:21,214 INFO [Flow Service Tasks Thread-1] 
> o.a.nifi.controller.StandardFlowService Saved flow controller 
> org.apache.nifi.controller.FlowController@33ab3784 // Another save pending = 
> false
> 2021-08-06 11:18:31,134 WARN [Timer-Driven Process Thread-13] 
> redis.clients.jedis.JedisSentinelPool Cannot get master address from sentinel 
> running @ i-redis-01:26379. Reason: {}. Trying next one.
> redis.clients.jedis.exceptions.JedisConnectionException: 
> javax.net.ssl.SSLException: Read timed out
>  at redis.clients.jedis.Connection.flush(Connection.java:342)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to