nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aldrin Piri <aldrinp...@gmail.com>
Subject Re: nifi Cluster setup issue
Date Tue, 29 Sep 2015 23:26:45 GMT
Chakrader,

I suspect that the nifi.web.http.host property is not using the same
address as that specified and is transmitting "localhost" (the system's
response to a localhost hostname lookup from Java).  While the clustering
protocol communicates via the properties you list, the actual
command-control and replication of requests from master to slave nodes is
carried out via the REST API which also runs on the web tier.  The system's
hostname, as previously determined, is transmitted as part of the
clustering handshake.

Either the system needs to have it report a valid hostname or a host needs
to be specified for nifi.web.http.host.  In either case of hostname or
specified host, each must be network reachable from the master and able to
be bound to locally within your server.

Let us know if you need additional direction and we'd be happy to help you
through the process.

Thanks!

On Tue, Sep 29, 2015 at 6:56 PM, Chakrader Dewaragatla <
Chakrader.Dewaragatla@lifelock.com> wrote:

> Hi – We are exploring nifi for our workflow management, I have a cluster
> setup with 3 nodes. One as master and rest as slaves.
>
> I see following error when I try to access the nifi workflow webpage.
>
> 2015-09-29 22:46:13,263 WARN [NiFi Web Server-23]
> o.a.n.c.m.impl.HttpRequestReplicatorImpl Node request for
> [id=7481fca5-930c-4d4b-84a3-66cc62b4e2d3, apiAddress=localhost,
> apiPort=8080, socketAddress=localhost, socketPort=3002] encountered
> exception: java.util.concurrent.ExecutionException:
> com.sun.jersey.api.client.ClientHandlerException:
> java.net.ConnectException: Connection refused
>
> 2015-09-29 22:46:13,263 WARN [NiFi Web Server-23]
> o.a.n.c.m.impl.HttpRequestReplicatorImpl Node request for
> [id=0abd8295-34a3-4bf7-ab06-1b6b94014740, apiAddress=localhost,
> apiPort=8080, socketAddress=10.233.2.42, socketPort=3002] encountered
> exception: java.util.concurrent.ExecutionException:
> com.sun.jersey.api.client.ClientHandlerException:
> java.net.ConnectException: Connection refused
>
> 2015-09-29 22:46:13,264 INFO [NiFi Web Server-23]
> o.a.n.c.m.e.NoConnectedNodesException
> org.apache.nifi.cluster.manager.exception.NoResponseFromNodesException: No
> nodes were able to process this request.. Returning Conflict response.
>
>
> Master is not hybrid, I wonder why it is trying to self connect 3002.
>
>
> Master settings:
>
> # cluster manager properties (only configure for cluster manager) #
>
> nifi.cluster.is.manager=true
>
> nifi.cluster.manager.address=10.233.2.40
>
> nifi.cluster.manager.protocol.port=3001
>
> nifi.cluster.manager.node.firewall.file=
>
> nifi.cluster.manager.node.event.history.size=10
>
> nifi.cluster.manager.node.api.connection.timeout=30 sec
>
> nifi.cluster.manager.node.api.read.timeout=30 sec
>
> nifi.cluster.manager.node.api.request.threads=10
>
> nifi.cluster.manager.flow.retrieval.delay=5 sec
>
> nifi.cluster.manager.protocol.threads=10
>
> nifi.cluster.manager.safemode.duration=0 sec
>
>
> Slave settings:
>
> # cluster node properties (only configure for cluster nodes) #
>
> nifi.cluster.is.node=true
>
> nifi.cluster.node.address=10.233.2.42
>
> nifi.cluster.node.protocol.port=3002
>
> nifi.cluster.node.protocol.threads=2
>
> # if multicast is not used, nifi.cluster.node.unicast.xxx must have same
> values as nifi.cluster.manager.xxx #
>
> nifi.cluster.node.unicast.manager.address=10.233.2.40
>
> nifi.cluster.node.unicast.manager.protocol.port=3001
>
>
>
>
> ------------------------------
> The information contained in this transmission may contain privileged and
> confidential information. It is intended only for the use of the person(s)
> named above. If you are not the intended recipient, you are hereby notified
> that any review, dissemination, distribution or duplication of this
> communication is strictly prohibited. If you are not the intended
> recipient, please contact the sender by reply email and destroy all copies
> of the original message.
> ------------------------------
>

Mime
View raw message