Re: BUG??? NiFi 1.13.2 Cluster Load Balance binds to localhost and is not accessible
Adding this line in the nifi.properties gets it to work: nifi.cluster.load.balance.address=0.0.0.0 There are a mismatch between nifi.properties and the java file handling the properties nifi.properties: nifi.cluster.load.balance.host nifi-commons/nifi-properties/src/main/java/org/apache/nifi/util/NiFiProperties.java: nifi.cluster.load.balance.address kind regards Jens Den fre. 11. jun. 2021 kl. 06.54 skrev Jens M. Kofoed < jmkofoed@gmail.com>: > I found out that another user has reported the same bug in JIRA: > https://issues.apache.org/jira/browse/NIFI-8643 > > so I'm not the only one, seeing this problem. > Kind regards > Jens > > Den tor. 10. jun. 2021 kl. 20.08 skrev Jens M. Kofoed < > jmkofoed@gmail.com>: > >> I have also tried to not specify any load balance host: >> nifi.cluster.load.balance.host= >> >> In the documentation is says: "If not specified, will default to the >> value used by the nifi.cluster.node.address property." and this port is >> working and bind to 0.0.0.0 >> >> Kind regards >> Jens >> >> Den tor. 10. jun. 2021 kl. 19.51 skrev Jens M. Kofoed < >> jmkofoed@gmail.com>: >> >>> Joe, Sorry if there is a space in the mail. There is no spaces in the >>> original config. I had to change the original address with an anonymous >>> >>> /jens >>> >>> Den 10. jun. 2021 kl. 19.31 skrev Joe Gresock : >>> >>> Jens, >>> >>> Can you try removing the space from the nifi.cluster.load.balance.host >>> property and see what happens? >>> >>> On Thu, Jun 10, 2021 at 1:23 PM Jens M. Kofoed >>> wrote: >>> Dear Community I have installed and configured a 3 node secured NiFi cluster with NiFi 1.13.2, Java 8 on Ubuntu 20.04. I was wondering why the cluster didn't load balance flowfiles after I configured Round Robins between a ListFTP and FetchFTP Process. (Other mails earlier today: Round Robin not working NiFi) After many attempt to find and fix the issues I notes that the load balance port 6342 was bind to localhost and not 0.0.0.0. > netstat -l Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp0 0 0.0.0.0:90900.0.0.0:* LISTEN tcp0 0 0.0.0.0:94430.0.0.0:* LISTEN tcp0 0 localhost:6342 0.0.0.0:* LISTEN tcp0 0 localhost:42603 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN tcp0 0 node01.domain.com:8443 0.0.0.0:* LISTEN tcp6 0 0 localhost:42101 [::]:* LISTEN tcp6 0 0 [::]:ssh[::]:* LISTEN raw6 0 0 [::]:ipv6-icmp [::]:* 7 Part of the configuration is like this: nifi.web.https.host=node1.domain.com nifi.web.https.port=8443 nifi.web.https.network.interface.default=ens192 nifi.cluster.is.node=true nifi.cluster.node.address=node01.domain.com nifi.cluster.node.protocol.port=9443 nifi.cluster.node.protocol.threads=10 nifi.cluster.node.protocol.max.threads=50 nifi.cluster.node.event.history.size=25 nifi.cluster.node.connection.timeout=5 sec nifi.cluster.node.read.timeout=5 sec nifi.cluster.node.max.concurrent.requests=100 nifi.cluster.firewall.file= nifi.cluster.flow.election.max.wait.time=5 mins nifi.cluster.flow.election.max.candidates=3 # cluster load balancing properties # nifi.cluster.load.balance.host= node01.domain.com nifi.cluster.load.balance.port=6342 nifi.cluster.load.balance.connections.per.node=4 nifi.cluster.load.balance.max.thread.count=8 nifi.cluster.load.balance.comms.timeout=30 sec Errors in nifi-app.log 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient Unable to connect to node3.domain.com:8443 for load balancing java.net.ConnectException: Connection refused 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient Unable to connect to node2.domain.com:8443 for load balancing java.net.ConnectException: Connection refused The question is: Why does the error messages say: Unable to connect to node2.domain.com:8443 for load balancing Shouldn't it be port 6342? Why does this port bind to localhost while all other ports bind to 0.0.0.0 or node01.domain.com??? kind regards Jens >>>
Re: BUG??? NiFi 1.13.2 Cluster Load Balance binds to localhost and is not accessible
I found out that another user has reported the same bug in JIRA: https://issues.apache.org/jira/browse/NIFI-8643 so I'm not the only one, seeing this problem. Kind regards Jens Den tor. 10. jun. 2021 kl. 20.08 skrev Jens M. Kofoed < jmkofoed@gmail.com>: > I have also tried to not specify any load balance host: > nifi.cluster.load.balance.host= > > In the documentation is says: "If not specified, will default to the value > used by the nifi.cluster.node.address property." and this port is working > and bind to 0.0.0.0 > > Kind regards > Jens > > Den tor. 10. jun. 2021 kl. 19.51 skrev Jens M. Kofoed < > jmkofoed@gmail.com>: > >> Joe, Sorry if there is a space in the mail. There is no spaces in the >> original config. I had to change the original address with an anonymous >> >> /jens >> >> Den 10. jun. 2021 kl. 19.31 skrev Joe Gresock : >> >> Jens, >> >> Can you try removing the space from the nifi.cluster.load.balance.host >> property and see what happens? >> >> On Thu, Jun 10, 2021 at 1:23 PM Jens M. Kofoed >> wrote: >> >>> Dear Community >>> >>> I have installed and configured a 3 node secured NiFi cluster with NiFi >>> 1.13.2, Java 8 on Ubuntu 20.04. >>> I was wondering why the cluster didn't load balance flowfiles after I >>> configured Round Robins between a ListFTP and FetchFTP Process. (Other >>> mails earlier today: Round Robin not working NiFi) >>> After many attempt to find and fix the issues I notes that the load >>> balance port 6342 was bind to localhost and not 0.0.0.0. >>> >>> > netstat -l >>> Active Internet connections (only servers) >>> Proto Recv-Q Send-Q Local Address Foreign Address State >>> tcp0 0 0.0.0.0:90900.0.0.0:* >>> LISTEN >>> tcp0 0 0.0.0.0:94430.0.0.0:* >>> LISTEN >>> tcp0 0 localhost:6342 0.0.0.0:* >>> LISTEN >>> tcp0 0 localhost:42603 0.0.0.0:* >>> LISTEN >>> tcp0 0 0.0.0.0:ssh 0.0.0.0:* >>> LISTEN >>> tcp0 0 node01.domain.com:8443 0.0.0.0:* >>> LISTEN >>> tcp6 0 0 localhost:42101 [::]:* >>> LISTEN >>> tcp6 0 0 [::]:ssh[::]:* >>> LISTEN >>> raw6 0 0 [::]:ipv6-icmp [::]:* 7 >>> >>> Part of the configuration is like this: >>> nifi.web.https.host=node1.domain.com >>> nifi.web.https.port=8443 >>> nifi.web.https.network.interface.default=ens192 >>> nifi.cluster.is.node=true >>> nifi.cluster.node.address=node01.domain.com >>> nifi.cluster.node.protocol.port=9443 >>> nifi.cluster.node.protocol.threads=10 >>> nifi.cluster.node.protocol.max.threads=50 >>> nifi.cluster.node.event.history.size=25 >>> nifi.cluster.node.connection.timeout=5 sec >>> nifi.cluster.node.read.timeout=5 sec >>> nifi.cluster.node.max.concurrent.requests=100 >>> nifi.cluster.firewall.file= >>> nifi.cluster.flow.election.max.wait.time=5 mins >>> nifi.cluster.flow.election.max.candidates=3 >>> >>> # cluster load balancing properties # >>> nifi.cluster.load.balance.host= node01.domain.com >>> nifi.cluster.load.balance.port=6342 >>> nifi.cluster.load.balance.connections.per.node=4 >>> nifi.cluster.load.balance.max.thread.count=8 >>> nifi.cluster.load.balance.comms.timeout=30 sec >>> >>> Errors in nifi-app.log >>> 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] >>> org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient >>> Unable to connect to node3.domain.com:8443 for load balancing >>> java.net.ConnectException: Connection refused >>> 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] >>> org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient >>> Unable to connect to node2.domain.com:8443 for load balancing >>> java.net.ConnectException: Connection refused >>> >>> The question is: >>> Why does the error messages say: Unable to connect to >>> node2.domain.com:8443 for load balancing >>> Shouldn't it be port 6342? >>> Why does this port bind to localhost while all other ports bind to >>> 0.0.0.0 or node01.domain.com??? >>> >>> kind regards >>> Jens >>> >>
Re: BUG??? NiFi 1.13.2 Cluster Load Balance binds to localhost and is not accessible
I have also tried to not specify any load balance host: nifi.cluster.load.balance.host= In the documentation is says: "If not specified, will default to the value used by the nifi.cluster.node.address property." and this port is working and bind to 0.0.0.0 Kind regards Jens Den tor. 10. jun. 2021 kl. 19.51 skrev Jens M. Kofoed < jmkofoed@gmail.com>: > Joe, Sorry if there is a space in the mail. There is no spaces in the > original config. I had to change the original address with an anonymous > > /jens > > Den 10. jun. 2021 kl. 19.31 skrev Joe Gresock : > > Jens, > > Can you try removing the space from the nifi.cluster.load.balance.host > property and see what happens? > > On Thu, Jun 10, 2021 at 1:23 PM Jens M. Kofoed > wrote: > >> Dear Community >> >> I have installed and configured a 3 node secured NiFi cluster with NiFi >> 1.13.2, Java 8 on Ubuntu 20.04. >> I was wondering why the cluster didn't load balance flowfiles after I >> configured Round Robins between a ListFTP and FetchFTP Process. (Other >> mails earlier today: Round Robin not working NiFi) >> After many attempt to find and fix the issues I notes that the load >> balance port 6342 was bind to localhost and not 0.0.0.0. >> >> > netstat -l >> Active Internet connections (only servers) >> Proto Recv-Q Send-Q Local Address Foreign Address State >> tcp0 0 0.0.0.0:90900.0.0.0:* >> LISTEN >> tcp0 0 0.0.0.0:94430.0.0.0:* >> LISTEN >> tcp0 0 localhost:6342 0.0.0.0:* >> LISTEN >> tcp0 0 localhost:42603 0.0.0.0:* >> LISTEN >> tcp0 0 0.0.0.0:ssh 0.0.0.0:* >> LISTEN >> tcp0 0 node01.domain.com:8443 0.0.0.0:* LISTEN >> tcp6 0 0 localhost:42101 [::]:* LISTEN >> tcp6 0 0 [::]:ssh[::]:* LISTEN >> raw6 0 0 [::]:ipv6-icmp [::]:* 7 >> >> Part of the configuration is like this: >> nifi.web.https.host=node1.domain.com >> nifi.web.https.port=8443 >> nifi.web.https.network.interface.default=ens192 >> nifi.cluster.is.node=true >> nifi.cluster.node.address=node01.domain.com >> nifi.cluster.node.protocol.port=9443 >> nifi.cluster.node.protocol.threads=10 >> nifi.cluster.node.protocol.max.threads=50 >> nifi.cluster.node.event.history.size=25 >> nifi.cluster.node.connection.timeout=5 sec >> nifi.cluster.node.read.timeout=5 sec >> nifi.cluster.node.max.concurrent.requests=100 >> nifi.cluster.firewall.file= >> nifi.cluster.flow.election.max.wait.time=5 mins >> nifi.cluster.flow.election.max.candidates=3 >> >> # cluster load balancing properties # >> nifi.cluster.load.balance.host= node01.domain.com >> nifi.cluster.load.balance.port=6342 >> nifi.cluster.load.balance.connections.per.node=4 >> nifi.cluster.load.balance.max.thread.count=8 >> nifi.cluster.load.balance.comms.timeout=30 sec >> >> Errors in nifi-app.log >> 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] >> org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient >> Unable to connect to node3.domain.com:8443 for load balancing >> java.net.ConnectException: Connection refused >> 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] >> org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient >> Unable to connect to node2.domain.com:8443 for load balancing >> java.net.ConnectException: Connection refused >> >> The question is: >> Why does the error messages say: Unable to connect to >> node2.domain.com:8443 for load balancing >> Shouldn't it be port 6342? >> Why does this port bind to localhost while all other ports bind to >> 0.0.0.0 or node01.domain.com??? >> >> kind regards >> Jens >> >
Re: BUG??? NiFi 1.13.2 Cluster Load Balance binds to localhost and is not accessible
Joe, Sorry if there is a space in the mail. There is no spaces in the original config. I had to change the original address with an anonymous /jens > Den 10. jun. 2021 kl. 19.31 skrev Joe Gresock : > > Jens, > > Can you try removing the space from the nifi.cluster.load.balance.host > property and see what happens? > >> On Thu, Jun 10, 2021 at 1:23 PM Jens M. Kofoed >> wrote: >> Dear Community >> >> I have installed and configured a 3 node secured NiFi cluster with NiFi >> 1.13.2, Java 8 on Ubuntu 20.04. >> I was wondering why the cluster didn't load balance flowfiles after I >> configured Round Robins between a ListFTP and FetchFTP Process. (Other mails >> earlier today: Round Robin not working NiFi) >> After many attempt to find and fix the issues I notes that the load balance >> port 6342 was bind to localhost and not 0.0.0.0. >> >> > netstat -l >> Active Internet connections (only servers) >> Proto Recv-Q Send-Q Local Address Foreign Address State >> tcp0 0 0.0.0.0:90900.0.0.0:* LISTEN >> tcp0 0 0.0.0.0:94430.0.0.0:* LISTEN >> tcp0 0 localhost:6342 0.0.0.0:* LISTEN >> tcp0 0 localhost:42603 0.0.0.0:* LISTEN >> tcp0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN >> tcp0 0 node01.domain.com:8443 0.0.0.0:* LISTEN >> tcp6 0 0 localhost:42101 [::]:* LISTEN >> tcp6 0 0 [::]:ssh[::]:* LISTEN >> raw6 0 0 [::]:ipv6-icmp [::]:* 7 >> >> Part of the configuration is like this: >> nifi.web.https.host=node1.domain.com >> nifi.web.https.port=8443 >> nifi.web.https.network.interface.default=ens192 >> nifi.cluster.is.node=true >> nifi.cluster.node.address=node01.domain.com >> nifi.cluster.node.protocol.port=9443 >> nifi.cluster.node.protocol.threads=10 >> nifi.cluster.node.protocol.max.threads=50 >> nifi.cluster.node.event.history.size=25 >> nifi.cluster.node.connection.timeout=5 sec >> nifi.cluster.node.read.timeout=5 sec >> nifi.cluster.node.max.concurrent.requests=100 >> nifi.cluster.firewall.file= >> nifi.cluster.flow.election.max.wait.time=5 mins >> nifi.cluster.flow.election.max.candidates=3 >> >> # cluster load balancing properties # >> nifi.cluster.load.balance.host= node01.domain.com >> nifi.cluster.load.balance.port=6342 >> nifi.cluster.load.balance.connections.per.node=4 >> nifi.cluster.load.balance.max.thread.count=8 >> nifi.cluster.load.balance.comms.timeout=30 sec >> >> Errors in nifi-app.log >> 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] >> org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient >> Unable to connect to node3.domain.com:8443 for load balancing >> java.net.ConnectException: Connection refused >> 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] >> org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient >> Unable to connect to node2.domain.com:8443 for load balancing >> java.net.ConnectException: Connection refused >> >> The question is: >> Why does the error messages say: Unable to connect to node2.domain.com:8443 >> for load balancing >> Shouldn't it be port 6342? >> Why does this port bind to localhost while all other ports bind to 0.0.0.0 >> or node01.domain.com??? >> >> kind regards >> Jens
Re: BUG??? NiFi 1.13.2 Cluster Load Balance binds to localhost and is not accessible
Jens, Can you try removing the space from the nifi.cluster.load.balance.host property and see what happens? On Thu, Jun 10, 2021 at 1:23 PM Jens M. Kofoed wrote: > Dear Community > > I have installed and configured a 3 node secured NiFi cluster with NiFi > 1.13.2, Java 8 on Ubuntu 20.04. > I was wondering why the cluster didn't load balance flowfiles after I > configured Round Robins between a ListFTP and FetchFTP Process. (Other > mails earlier today: Round Robin not working NiFi) > After many attempt to find and fix the issues I notes that the load > balance port 6342 was bind to localhost and not 0.0.0.0. > > > netstat -l > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address State > tcp0 0 0.0.0.0:90900.0.0.0:* LISTEN > tcp0 0 0.0.0.0:94430.0.0.0:* LISTEN > tcp0 0 localhost:6342 0.0.0.0:* LISTEN > tcp0 0 localhost:42603 0.0.0.0:* LISTEN > tcp0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN > tcp0 0 node01.domain.com:8443 0.0.0.0:* LISTEN > tcp6 0 0 localhost:42101 [::]:* LISTEN > tcp6 0 0 [::]:ssh[::]:* LISTEN > raw6 0 0 [::]:ipv6-icmp [::]:* 7 > > Part of the configuration is like this: > nifi.web.https.host=node1.domain.com > nifi.web.https.port=8443 > nifi.web.https.network.interface.default=ens192 > nifi.cluster.is.node=true > nifi.cluster.node.address=node01.domain.com > nifi.cluster.node.protocol.port=9443 > nifi.cluster.node.protocol.threads=10 > nifi.cluster.node.protocol.max.threads=50 > nifi.cluster.node.event.history.size=25 > nifi.cluster.node.connection.timeout=5 sec > nifi.cluster.node.read.timeout=5 sec > nifi.cluster.node.max.concurrent.requests=100 > nifi.cluster.firewall.file= > nifi.cluster.flow.election.max.wait.time=5 mins > nifi.cluster.flow.election.max.candidates=3 > > # cluster load balancing properties # > nifi.cluster.load.balance.host= node01.domain.com > nifi.cluster.load.balance.port=6342 > nifi.cluster.load.balance.connections.per.node=4 > nifi.cluster.load.balance.max.thread.count=8 > nifi.cluster.load.balance.comms.timeout=30 sec > > Errors in nifi-app.log > 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] > org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient > Unable to connect to node3.domain.com:8443 for load balancing > java.net.ConnectException: Connection refused > 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] > org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient > Unable to connect to node2.domain.com:8443 for load balancing > java.net.ConnectException: Connection refused > > The question is: > Why does the error messages say: Unable to connect to > node2.domain.com:8443 for load balancing > Shouldn't it be port 6342? > Why does this port bind to localhost while all other ports bind to 0.0.0.0 > or node01.domain.com??? > > kind regards > Jens >
BUG??? NiFi 1.13.2 Cluster Load Balance binds to localhost and is not accessible
Dear Community I have installed and configured a 3 node secured NiFi cluster with NiFi 1.13.2, Java 8 on Ubuntu 20.04. I was wondering why the cluster didn't load balance flowfiles after I configured Round Robins between a ListFTP and FetchFTP Process. (Other mails earlier today: Round Robin not working NiFi) After many attempt to find and fix the issues I notes that the load balance port 6342 was bind to localhost and not 0.0.0.0. > netstat -l Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp0 0 0.0.0.0:90900.0.0.0:* LISTEN tcp0 0 0.0.0.0:94430.0.0.0:* LISTEN tcp0 0 localhost:6342 0.0.0.0:* LISTEN tcp0 0 localhost:42603 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN tcp0 0 node01.domain.com:8443 0.0.0.0:* LISTEN tcp6 0 0 localhost:42101 [::]:* LISTEN tcp6 0 0 [::]:ssh[::]:* LISTEN raw6 0 0 [::]:ipv6-icmp [::]:* 7 Part of the configuration is like this: nifi.web.https.host=node1.domain.com nifi.web.https.port=8443 nifi.web.https.network.interface.default=ens192 nifi.cluster.is.node=true nifi.cluster.node.address=node01.domain.com nifi.cluster.node.protocol.port=9443 nifi.cluster.node.protocol.threads=10 nifi.cluster.node.protocol.max.threads=50 nifi.cluster.node.event.history.size=25 nifi.cluster.node.connection.timeout=5 sec nifi.cluster.node.read.timeout=5 sec nifi.cluster.node.max.concurrent.requests=100 nifi.cluster.firewall.file= nifi.cluster.flow.election.max.wait.time=5 mins nifi.cluster.flow.election.max.candidates=3 # cluster load balancing properties # nifi.cluster.load.balance.host= node01.domain.com nifi.cluster.load.balance.port=6342 nifi.cluster.load.balance.connections.per.node=4 nifi.cluster.load.balance.max.thread.count=8 nifi.cluster.load.balance.comms.timeout=30 sec Errors in nifi-app.log 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient Unable to connect to node3.domain.com:8443 for load balancing java.net.ConnectException: Connection refused 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient Unable to connect to node2.domain.com:8443 for load balancing java.net.ConnectException: Connection refused The question is: Why does the error messages say: Unable to connect to node2.domain.com:8443 for load balancing Shouldn't it be port 6342? Why does this port bind to localhost while all other ports bind to 0.0.0.0 or node01.domain.com??? kind regards Jens
Re: Round Robin not working NiFi 1.13.2
In the beginning both parameters was set: nifi.cluster.is.node=true nifi.cluster.node.address=node01.domain.com nifi.cluster.node.protocol.port=9443 nifi.cluster.node.protocol.threads=10 nifi.cluster.node.protocol.max.threads=50 nifi.cluster.node.event.history.size=25 nifi.cluster.node.connection.timeout=5 sec nifi.cluster.node.read.timeout=5 sec nifi.cluster.node.max.concurrent.requests=100 nifi.cluster.firewall.file= nifi.cluster.flow.election.max.wait.time=5 mins nifi.cluster.flow.election.max.candidates=3 # cluster load balancing properties # nifi.cluster.load.balance.host= node01.domain.com nifi.cluster.load.balance.port=6342 nifi.cluster.load.balance.connections.per.node=4 nifi.cluster.load.balance.max.thread.count=8 nifi.cluster.load.balance.comms.timeout=30 sec If have testet multiple combination of host names. the "funny" part is that port 9443 binds to 0.0.0.0: netstat -l Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp0 0 0.0.0.0:90900.0.0.0:* LISTEN tcp0 0 0.0.0.0:94430.0.0.0:* LISTEN tcp0 0 localhost:6342 0.0.0.0:* LISTEN tcp0 0 localhost:42603 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN tcp0 0 node01.domain.com:8443 0.0.0.0:* LISTEN tcp6 0 0 localhost:42101 [::]:* LISTEN tcp6 0 0 [::]:ssh[::]:* LISTEN raw6 0 0 [::]:ipv6-icmp [::]:* 7 regards Jens Den tor. 10. jun. 2021 kl. 16.53 skrev Joe Gresock : > Looking at the code, it appears that if nifi.cluster.load.balance.address > is not set, it falls back to choosing nifi.cluster.node.address. If this > is not provided, it finally falls back to localhost. > > I'd recommend setting nifi.cluster.node.address at minimum, and you might > as well also set nifi.cluster.load.balance.address in order to be explicit. > > On Thu, Jun 10, 2021 at 10:45 AM Jens M. Kofoed > wrote: > >> Hi Joe >> >> I just found out that port 6342 is bound to localhost. Why >> In the last build NIFI is bound to localhost as standard if not >> specifying which interface to use: >> nifi.web.https.host=node1.domain.com >> nifi.web.https.port=8443 >> nifi.web.https.network.interface.default=ens192<- If this is not >> configured the UI is bound to localhost. >> >> But how can I configure port 6342 to bound to any interface??? >> >> kind regards >> Jens >> >> >> Den tor. 10. jun. 2021 kl. 16.32 skrev Joe Gresock : >> >>> Ok, and just to confirm, you've verified that each node can talk to the >>> others over port 6342? >>> >>> On Thu, Jun 10, 2021 at 10:29 AM Jens M. Kofoed >>> wrote: >>> I have the same error for node2 as well. All 3 nodes can talk to each other. If I use a remote process group and connect to an "remote" input port, everything works fine. This is a work around for round robin. My configuration for cluster load balance is the default. nifi.cluster.load.balance.host= nifi.cluster.load.balance.port=6342 nifi.cluster.load.balance.connections.per.node=4 nifi.cluster.load.balance.max.thread.count=8 nifi.cluster.load.balance.comms.timeout=30 sec kind regards Jens Den tor. 10. jun. 2021 kl. 16.18 skrev Joe Gresock >>> >: > That would seem to be the culprit :) It sounds like your other nodes > can't connect to node3 over port 8443. Have you verified that the port is > open? Same question for all other ports configured in your > nifi.properties. > > On Thu, Jun 10, 2021 at 10:08 AM Jens M. Kofoed < > jmkofoed@gmail.com> wrote: > >> Hi Joe >> >> Thanks for replaying :-) >> Looking at status history for the fetchFTP and all the other >> processers in the flow it is only the primary node which has processed >> flowfiles. >> I have created clusters before with no issues, but there must be >> something tricky which I'm missing. >> >> I found this error in the log which explain why it is only the >> primary node >> 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] >> org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient >> Unable to connect to node3.domain.com:8443 for load balancing >> java.net.ConnectException: Connection refused >> >> But I don't know why the Connection should be refused. I can't find >> any other errors about connections. And know I have added the node group >> into all policies, so all nodes should have all access rights. >> >> Any advice for future investigation? >> >> kind regards >> Jens >> >> Den tor. 10. jun. 2021 kl. 15.36 skrev Joe Gresock < >>
Re: Round Robin not working NiFi 1.13.2
Looking at the code, it appears that if nifi.cluster.load.balance.address is not set, it falls back to choosing nifi.cluster.node.address. If this is not provided, it finally falls back to localhost. I'd recommend setting nifi.cluster.node.address at minimum, and you might as well also set nifi.cluster.load.balance.address in order to be explicit. On Thu, Jun 10, 2021 at 10:45 AM Jens M. Kofoed wrote: > Hi Joe > > I just found out that port 6342 is bound to localhost. Why > In the last build NIFI is bound to localhost as standard if not specifying > which interface to use: > nifi.web.https.host=node1.domain.com > nifi.web.https.port=8443 > nifi.web.https.network.interface.default=ens192<- If this is not > configured the UI is bound to localhost. > > But how can I configure port 6342 to bound to any interface??? > > kind regards > Jens > > > Den tor. 10. jun. 2021 kl. 16.32 skrev Joe Gresock : > >> Ok, and just to confirm, you've verified that each node can talk to the >> others over port 6342? >> >> On Thu, Jun 10, 2021 at 10:29 AM Jens M. Kofoed >> wrote: >> >>> I have the same error for node2 as well. >>> All 3 nodes can talk to each other. If I use a remote process group and >>> connect to an "remote" input port, everything works fine. This is a work >>> around for round robin. >>> My configuration for cluster load balance is the default. >>> nifi.cluster.load.balance.host= >>> nifi.cluster.load.balance.port=6342 >>> nifi.cluster.load.balance.connections.per.node=4 >>> nifi.cluster.load.balance.max.thread.count=8 >>> nifi.cluster.load.balance.comms.timeout=30 sec >>> >>> kind regards >>> Jens >>> >>> >>> Den tor. 10. jun. 2021 kl. 16.18 skrev Joe Gresock : >>> That would seem to be the culprit :) It sounds like your other nodes can't connect to node3 over port 8443. Have you verified that the port is open? Same question for all other ports configured in your nifi.properties. On Thu, Jun 10, 2021 at 10:08 AM Jens M. Kofoed wrote: > Hi Joe > > Thanks for replaying :-) > Looking at status history for the fetchFTP and all the other > processers in the flow it is only the primary node which has processed > flowfiles. > I have created clusters before with no issues, but there must be > something tricky which I'm missing. > > I found this error in the log which explain why it is only the primary > node > 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] > org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient > Unable to connect to node3.domain.com:8443 for load balancing > java.net.ConnectException: Connection refused > > But I don't know why the Connection should be refused. I can't find > any other errors about connections. And know I have added the node group > into all policies, so all nodes should have all access rights. > > Any advice for future investigation? > > kind regards > Jens > > Den tor. 10. jun. 2021 kl. 15.36 skrev Joe Gresock >: > >> Hi Jens, >> >> Out of curiosity, when you run the FetchFTP processor, what does the >> Status History of that processor show? Is the processor processing files >> on all of your nodes or just the primary? >> >> On Thu, Jun 10, 2021 at 9:07 AM Jens M. Kofoed < >> jmkofoed@gmail.com> wrote: >> >>> Dear community >>> >>> I have created a 3 node cluster with NiFi 1.13.2, java 8 on a ubuntu >>> 20.04. >>> I have a ListFTP Process running on primary node only -> FetchFTP >>> with Round Robin on the connection. But if I stop the FetchFTP Process >>> and >>> looking at the queue all flowfiles are listed to be on the same node. >>> Which >>> is also the primary node. >>> >>> Just for testing purpose, I've tried to set round robin on other >>> connection but all files stays on primary node. I have been looking in >>> the >>> logs but can't find any errors yet. >>> >>> Please advice? >>> kind regards >>> Jens >>> >>
Re: Round Robin not working NiFi 1.13.2
Hi Joe I just found out that port 6342 is bound to localhost. Why In the last build NIFI is bound to localhost as standard if not specifying which interface to use: nifi.web.https.host=node1.domain.com nifi.web.https.port=8443 nifi.web.https.network.interface.default=ens192<- If this is not configured the UI is bound to localhost. But how can I configure port 6342 to bound to any interface??? kind regards Jens Den tor. 10. jun. 2021 kl. 16.32 skrev Joe Gresock : > Ok, and just to confirm, you've verified that each node can talk to the > others over port 6342? > > On Thu, Jun 10, 2021 at 10:29 AM Jens M. Kofoed > wrote: > >> I have the same error for node2 as well. >> All 3 nodes can talk to each other. If I use a remote process group and >> connect to an "remote" input port, everything works fine. This is a work >> around for round robin. >> My configuration for cluster load balance is the default. >> nifi.cluster.load.balance.host= >> nifi.cluster.load.balance.port=6342 >> nifi.cluster.load.balance.connections.per.node=4 >> nifi.cluster.load.balance.max.thread.count=8 >> nifi.cluster.load.balance.comms.timeout=30 sec >> >> kind regards >> Jens >> >> >> Den tor. 10. jun. 2021 kl. 16.18 skrev Joe Gresock : >> >>> That would seem to be the culprit :) It sounds like your other nodes >>> can't connect to node3 over port 8443. Have you verified that the port is >>> open? Same question for all other ports configured in your nifi.properties. >>> >>> On Thu, Jun 10, 2021 at 10:08 AM Jens M. Kofoed >>> wrote: >>> Hi Joe Thanks for replaying :-) Looking at status history for the fetchFTP and all the other processers in the flow it is only the primary node which has processed flowfiles. I have created clusters before with no issues, but there must be something tricky which I'm missing. I found this error in the log which explain why it is only the primary node 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient Unable to connect to node3.domain.com:8443 for load balancing java.net.ConnectException: Connection refused But I don't know why the Connection should be refused. I can't find any other errors about connections. And know I have added the node group into all policies, so all nodes should have all access rights. Any advice for future investigation? kind regards Jens Den tor. 10. jun. 2021 kl. 15.36 skrev Joe Gresock >>> >: > Hi Jens, > > Out of curiosity, when you run the FetchFTP processor, what does the > Status History of that processor show? Is the processor processing files > on all of your nodes or just the primary? > > On Thu, Jun 10, 2021 at 9:07 AM Jens M. Kofoed > wrote: > >> Dear community >> >> I have created a 3 node cluster with NiFi 1.13.2, java 8 on a ubuntu >> 20.04. >> I have a ListFTP Process running on primary node only -> FetchFTP >> with Round Robin on the connection. But if I stop the FetchFTP Process >> and >> looking at the queue all flowfiles are listed to be on the same node. >> Which >> is also the primary node. >> >> Just for testing purpose, I've tried to set round robin on other >> connection but all files stays on primary node. I have been looking in >> the >> logs but can't find any errors yet. >> >> Please advice? >> kind regards >> Jens >> >
Re: Round Robin not working NiFi 1.13.2
Ok, and just to confirm, you've verified that each node can talk to the others over port 6342? On Thu, Jun 10, 2021 at 10:29 AM Jens M. Kofoed wrote: > I have the same error for node2 as well. > All 3 nodes can talk to each other. If I use a remote process group and > connect to an "remote" input port, everything works fine. This is a work > around for round robin. > My configuration for cluster load balance is the default. > nifi.cluster.load.balance.host= > nifi.cluster.load.balance.port=6342 > nifi.cluster.load.balance.connections.per.node=4 > nifi.cluster.load.balance.max.thread.count=8 > nifi.cluster.load.balance.comms.timeout=30 sec > > kind regards > Jens > > > Den tor. 10. jun. 2021 kl. 16.18 skrev Joe Gresock : > >> That would seem to be the culprit :) It sounds like your other nodes >> can't connect to node3 over port 8443. Have you verified that the port is >> open? Same question for all other ports configured in your nifi.properties. >> >> On Thu, Jun 10, 2021 at 10:08 AM Jens M. Kofoed >> wrote: >> >>> Hi Joe >>> >>> Thanks for replaying :-) >>> Looking at status history for the fetchFTP and all the other processers >>> in the flow it is only the primary node which has processed flowfiles. >>> I have created clusters before with no issues, but there must be >>> something tricky which I'm missing. >>> >>> I found this error in the log which explain why it is only the primary >>> node >>> 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] >>> org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient >>> Unable to connect to node3.domain.com:8443 for load balancing >>> java.net.ConnectException: Connection refused >>> >>> But I don't know why the Connection should be refused. I can't find any >>> other errors about connections. And know I have added the node group into >>> all policies, so all nodes should have all access rights. >>> >>> Any advice for future investigation? >>> >>> kind regards >>> Jens >>> >>> Den tor. 10. jun. 2021 kl. 15.36 skrev Joe Gresock : >>> Hi Jens, Out of curiosity, when you run the FetchFTP processor, what does the Status History of that processor show? Is the processor processing files on all of your nodes or just the primary? On Thu, Jun 10, 2021 at 9:07 AM Jens M. Kofoed wrote: > Dear community > > I have created a 3 node cluster with NiFi 1.13.2, java 8 on a ubuntu > 20.04. > I have a ListFTP Process running on primary node only -> FetchFTP with > Round Robin on the connection. But if I stop the FetchFTP Process and > looking at the queue all flowfiles are listed to be on the same node. > Which > is also the primary node. > > Just for testing purpose, I've tried to set round robin on other > connection but all files stays on primary node. I have been looking in the > logs but can't find any errors yet. > > Please advice? > kind regards > Jens >
Re: Round Robin not working NiFi 1.13.2
I have the same error for node2 as well. All 3 nodes can talk to each other. If I use a remote process group and connect to an "remote" input port, everything works fine. This is a work around for round robin. My configuration for cluster load balance is the default. nifi.cluster.load.balance.host= nifi.cluster.load.balance.port=6342 nifi.cluster.load.balance.connections.per.node=4 nifi.cluster.load.balance.max.thread.count=8 nifi.cluster.load.balance.comms.timeout=30 sec kind regards Jens Den tor. 10. jun. 2021 kl. 16.18 skrev Joe Gresock : > That would seem to be the culprit :) It sounds like your other nodes > can't connect to node3 over port 8443. Have you verified that the port is > open? Same question for all other ports configured in your nifi.properties. > > On Thu, Jun 10, 2021 at 10:08 AM Jens M. Kofoed > wrote: > >> Hi Joe >> >> Thanks for replaying :-) >> Looking at status history for the fetchFTP and all the other processers >> in the flow it is only the primary node which has processed flowfiles. >> I have created clusters before with no issues, but there must be >> something tricky which I'm missing. >> >> I found this error in the log which explain why it is only the primary >> node >> 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] >> org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient >> Unable to connect to node3.domain.com:8443 for load balancing >> java.net.ConnectException: Connection refused >> >> But I don't know why the Connection should be refused. I can't find any >> other errors about connections. And know I have added the node group into >> all policies, so all nodes should have all access rights. >> >> Any advice for future investigation? >> >> kind regards >> Jens >> >> Den tor. 10. jun. 2021 kl. 15.36 skrev Joe Gresock : >> >>> Hi Jens, >>> >>> Out of curiosity, when you run the FetchFTP processor, what does the >>> Status History of that processor show? Is the processor processing files >>> on all of your nodes or just the primary? >>> >>> On Thu, Jun 10, 2021 at 9:07 AM Jens M. Kofoed >>> wrote: >>> Dear community I have created a 3 node cluster with NiFi 1.13.2, java 8 on a ubuntu 20.04. I have a ListFTP Process running on primary node only -> FetchFTP with Round Robin on the connection. But if I stop the FetchFTP Process and looking at the queue all flowfiles are listed to be on the same node. Which is also the primary node. Just for testing purpose, I've tried to set round robin on other connection but all files stays on primary node. I have been looking in the logs but can't find any errors yet. Please advice? kind regards Jens >>>
Re: Round Robin not working NiFi 1.13.2
That would seem to be the culprit :) It sounds like your other nodes can't connect to node3 over port 8443. Have you verified that the port is open? Same question for all other ports configured in your nifi.properties. On Thu, Jun 10, 2021 at 10:08 AM Jens M. Kofoed wrote: > Hi Joe > > Thanks for replaying :-) > Looking at status history for the fetchFTP and all the other processers in > the flow it is only the primary node which has processed flowfiles. > I have created clusters before with no issues, but there must be something > tricky which I'm missing. > > I found this error in the log which explain why it is only the primary node > 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] > org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient > Unable to connect to node3.domain.com:8443 for load balancing > java.net.ConnectException: Connection refused > > But I don't know why the Connection should be refused. I can't find any > other errors about connections. And know I have added the node group into > all policies, so all nodes should have all access rights. > > Any advice for future investigation? > > kind regards > Jens > > Den tor. 10. jun. 2021 kl. 15.36 skrev Joe Gresock : > >> Hi Jens, >> >> Out of curiosity, when you run the FetchFTP processor, what does the >> Status History of that processor show? Is the processor processing files >> on all of your nodes or just the primary? >> >> On Thu, Jun 10, 2021 at 9:07 AM Jens M. Kofoed >> wrote: >> >>> Dear community >>> >>> I have created a 3 node cluster with NiFi 1.13.2, java 8 on a ubuntu >>> 20.04. >>> I have a ListFTP Process running on primary node only -> FetchFTP with >>> Round Robin on the connection. But if I stop the FetchFTP Process and >>> looking at the queue all flowfiles are listed to be on the same node. Which >>> is also the primary node. >>> >>> Just for testing purpose, I've tried to set round robin on other >>> connection but all files stays on primary node. I have been looking in the >>> logs but can't find any errors yet. >>> >>> Please advice? >>> kind regards >>> Jens >>> >>
Re: Round Robin not working NiFi 1.13.2
Hi Joe Thanks for replaying :-) Looking at status history for the fetchFTP and all the other processers in the flow it is only the primary node which has processed flowfiles. I have created clusters before with no issues, but there must be something tricky which I'm missing. I found this error in the log which explain why it is only the primary node 2021-06-10 16:00:22,078 ERROR [Load-Balanced Client Thread-1] org.apache.nifi.controller.queue.clustered.client.async.nio.NioAsyncLoadBalanceClient Unable to connect to node3.domain.com:8443 for load balancing java.net.ConnectException: Connection refused But I don't know why the Connection should be refused. I can't find any other errors about connections. And know I have added the node group into all policies, so all nodes should have all access rights. Any advice for future investigation? kind regards Jens Den tor. 10. jun. 2021 kl. 15.36 skrev Joe Gresock : > Hi Jens, > > Out of curiosity, when you run the FetchFTP processor, what does the > Status History of that processor show? Is the processor processing files > on all of your nodes or just the primary? > > On Thu, Jun 10, 2021 at 9:07 AM Jens M. Kofoed > wrote: > >> Dear community >> >> I have created a 3 node cluster with NiFi 1.13.2, java 8 on a ubuntu >> 20.04. >> I have a ListFTP Process running on primary node only -> FetchFTP with >> Round Robin on the connection. But if I stop the FetchFTP Process and >> looking at the queue all flowfiles are listed to be on the same node. Which >> is also the primary node. >> >> Just for testing purpose, I've tried to set round robin on other >> connection but all files stays on primary node. I have been looking in the >> logs but can't find any errors yet. >> >> Please advice? >> kind regards >> Jens >> >
Re: Round Robin not working NiFi 1.13.2
Hi Jens, Out of curiosity, when you run the FetchFTP processor, what does the Status History of that processor show? Is the processor processing files on all of your nodes or just the primary? On Thu, Jun 10, 2021 at 9:07 AM Jens M. Kofoed wrote: > Dear community > > I have created a 3 node cluster with NiFi 1.13.2, java 8 on a ubuntu 20.04. > I have a ListFTP Process running on primary node only -> FetchFTP with > Round Robin on the connection. But if I stop the FetchFTP Process and > looking at the queue all flowfiles are listed to be on the same node. Which > is also the primary node. > > Just for testing purpose, I've tried to set round robin on other > connection but all files stays on primary node. I have been looking in the > logs but can't find any errors yet. > > Please advice? > kind regards > Jens >
Round Robin not working NiFi 1.13.2
Dear community I have created a 3 node cluster with NiFi 1.13.2, java 8 on a ubuntu 20.04. I have a ListFTP Process running on primary node only -> FetchFTP with Round Robin on the connection. But if I stop the FetchFTP Process and looking at the queue all flowfiles are listed to be on the same node. Which is also the primary node. Just for testing purpose, I've tried to set round robin on other connection but all files stays on primary node. I have been looking in the logs but can't find any errors yet. Please advice? kind regards Jens
