You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Josef Zahner (JIRA)" <ji...@apache.org> on 2019/01/28 10:57:00 UTC

[jira] [Resolved] (NIFI-5976) RedisConnectionPoolService doesn't use connection string in standalone mode

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

Josef Zahner resolved NIFI-5976.
--------------------------------
       Resolution: Duplicate
    Fix Version/s: 1.9.0

Duplicate,... 
original ticket: https://issues.apache.org/jira/browse/NIFI-5830

> RedisConnectionPoolService doesn't use connection string in standalone mode
> ---------------------------------------------------------------------------
>
>                 Key: NIFI-5976
>                 URL: https://issues.apache.org/jira/browse/NIFI-5976
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.8.0
>         Environment: Centos 7
> Secured NiFi 2 Node Cluster
>            Reporter: Josef Zahner
>            Priority: Major
>             Fix For: 1.9.0
>
>
> The RedisConnectionPoolService in "Redis Mode - Standalone" doesn't use the "Connection String". If i insert _myhostname:6379_ it connects to _localhost:6379_ instead.
> *Verified by tcpdump*:
> {code:java}
> [tester@nifi-03 ~]$ sudo tcpdump -i any -s 1500 -X port 6379 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 1500 bytes 13:00:13.422299 IP localhost.52792 > localhost.6379: Flags [S], seq 2959469726, win 43690, options [mss 65495,sackOK,TS val 1907747964 ecr 0,nop,wscale 11], length 0 0x0000: 4500 003c 00e2 4000 4006 3bd8 7f00 0001 E..<..@.@.;..... 0x0010: 7f00 0001 ce38 18eb b065 ec9e 0000 0000 .....8...e...... 0x0020: a002 aaaa fe30 0000 0204 ffd7 0402 080a .....0.......... 0x0030: 71b5 ec7c 0000 0000 0103 030b 0000 0000 q..|............ 0x0040: 0000 0000 0000 0000 0000 0000 ............ 13:00:13.422318 IP localhost.6379 > localhost.52792: Flags [R.], seq 0, ack 2959469727, win 0, length 0 0x0000: 4500 0028 6d71 4000 4006 cf5c 7f00 0001 E..(mq@.@..\.... 0x0010: 7f00 0001 18eb ce38 0000 0000 b065 ec9f .......8.....e.. 0x0020: 5014 0000 2da5 0000 0000 0000 0000 0000 P...-........... 0x0030: 0000 0000 0000 0000
> {code}
>  
> *Workaround* (ssh tunnel localhost port 6379 to remote host):
> {code:java}
> ssh -f -C -N -L 127.0.0.1:6379:myhostname:6379 localhost
> {code}
>  
> Seems that I'm not the only one who has seen this:
> [https://lists.apache.org/thread.html/412ca5acf6e31ed56ae1f871edd96a65ea27fc0d3aad9183044dfbc4@%3Cusers.nifi.apache.org%3E]
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)