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 <jgres...@gmail.com>: > >> 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 >>> >>
