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 <jgres...@gmail.com>: > > 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 <jmkofoed....@gmail.com> > 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 >> tcp 0 0 0.0.0.0:9090 0.0.0.0:* >> LISTEN >> tcp 0 0 0.0.0.0:9443 0.0.0.0:* >> LISTEN >> tcp 0 0 localhost:6342 0.0.0.0:* >> LISTEN >> tcp 0 0 localhost:42603 0.0.0.0:* >> LISTEN >> tcp 0 0 0.0.0.0:ssh 0.0.0.0:* >> LISTEN >> tcp 0 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 >> >
