This is a bug. There are a mismatch between documentation, nifi.properties
and the java class handling the properties
https://issues.apache.org/jira/browse/NIFI-8643
kind regards
Jens
Den tor. 10. jun. 2021 kl. 17.01 skrev Jens M. Kofoed <
jmkofoed@gmail.com>:
> In the beginning both
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
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
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
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"
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.
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
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
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
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
10 matches
Mail list logo
