You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Paresh Shah <Pa...@lifelock.com> on 2016/02/03 05:40:14 UTC
Unable to communicate between two Nifi clusters.
We have multiple cluster setup.
Cluster 1:
NCM : 10.233.0.183:8080
Nodes: 10.233.0.156, 10.233.0.180
Cluster 2:
NCM : i-e9c63569.dev.aws.lifelock.ad
Nodes : i-e9c63569.dev.aws.lifelock.ad<http://i-e9c63569.dev.aws.lifelock.ad>, i-e9c63569.dev.aws.lifelock.ad
We were able to successfully connect the RPG from Cluster 1 to the remote input port. But are unable to send the data to the remote cluster. This means
We are able to log in to the cluster(s) and see that the nodes are connected.
Here’s snippets of the logs from the cluster that we are trying to send the data from.
2016-02-03 04:30:58,565 INFO [NiFi Web Server-236] org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) GET http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source ip: 10.233.0.156)
2016-02-03 04:31:06,093 INFO [NiFi Web Server-236] org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) GET http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/process-groups/ec38494d-b925-4afb-a0c0-2a02861ec03e/status (source ip: 172.16.2.33)
2016-02-03 04:31:06,210 INFO [NiFi Web Server-2695] org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) GET http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/status (source ip: 172.16.2.33)
2016-02-03 04:31:06,217 INFO [NiFi Web Server-1273] org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) GET http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/revision (source ip: 172.16.2.33)
2016-02-03 04:31:07,407 INFO [NiFi Web Server-2694] org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) GET http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source ip: 10.233.0.180)
2016-02-03 04:31:07,433 INFO [NiFi Web Server-2695] org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) GET http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source ip: 10.233.0.156)
________________________________
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.
________________________________
Re: Unable to communicate between two Nifi clusters.
Posted by Mark Payne <ma...@hotmail.com>.
Chakri,
When NiFi communicates via Site-to-Site, it connects to the HTTP interface only to determine what
the site-to-site socket port is. So on Cluster 2 NCM, check what value is set in the properties file for the
nifi.remote.input.socket.port - then try to telnet to that port. Do you have a firewall setup that could be
blocking that port?
> On Feb 3, 2016, at 2:30 AM, Chakrader Dewaragatla <Ch...@lifelock.com> wrote:
>
> Ricard - Yes, FQDN lookup works from the node.
>
> [root@ip-10-233-0-156 logs]# telnet i-e9c63569.dev.aws.lifelock.ad 8080
> Trying 10.228.68.219...
> Connected to i-e9c63569.dev.aws.lifelock.ad.
> Escape character is '^]'.
>
>
>
> On 2/2/16, 11:11 PM, "Richard Miskin" <r....@gmail.com> wrote:
>
>> It looks like you're using a fully qualified name in the node
>> configuration
>> but you've tested an IP address using telnet. Is
>> http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi correct?
>>
>> Richard
>>
>>
>> On Wednesday, 3 February 2016, Chakrader Dewaragatla <
>> Chakrader.Dewaragatla@lifelock.com> wrote:
>>
>>> On Cluster 1 salves, we notice time out connecting to Cluster 2 NCM.
>>>
>>> 2016-02-03 06:51:42,585 WARN [Timer-Driven Process Thread-4]
>>> o.a.n.r.c.socket.EndpointConnectionPool EndpointConnectionPool[Cluster
>>> URL=http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi] Unable to refresh
>>> Remote Group's peers due to {}
>>> java.net.ConnectException: Connection timed out
>>>
>>>
>>>
>>> Network ports/firewall seems to be ok.
>>>
>>> [root@ip-10-233-0-156 logs]# telnet 10.228.68.219 8080
>>> Trying 10.228.68.219...
>>> Connected to 10.228.68.219.
>>> Escape character is '^]'.
>>> ^\Connection closed by foreign host.
>>>
>>>
>>>
>>> Curl or wget works fine as well.
>>>
>>>
>>> On 2/2/16, 8:43 PM, "Paresh Shah" <Paresh.Shah@lifelock.com
>>> <javascript:;>>
>>> wrote:
>>>
>>>> More updates. Now the sending cluster reports that the nodes are
>>>> disconnected.
>>>>
>>>> ...
>>>> 2016-02-03 04:41:09,176 WARN [NiFi Web Server-313]
>>>> o.a.n.c.manager.impl.WebClusterManager All nodes failed to process URI
>>>>
>>>
>>> http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2
>>> -
>>>> 4
>>>
>>>> e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3a
>>>> df
>>>> 8
>>>> df113. As a result, no node will be disconnected from cluster
>>>> 2016-02-03 04:41:09,177 INFO [NiFi Web Server-313]
>>>> o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>> request:
>>>> org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
>>> All
>>>> nodes were disconnected as a result of applying request PUT
>>>>
>>>
>>> http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2
>>> -
>>>> 4
>>>
>>>> e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3a
>>>> df
>>>> 8
>>>> df113. Returning Internal Server Error response.
>>>> 2016-02-03 04:41:09,178 INFO [NiFi Web Server-348]
>>>> o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>> request:
>>>> org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>>>> Returning Internal Server Error response.
>>>> 2016-02-03 04:41:09,179 INFO [NiFi Web Server-365]
>>>> o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>> request:
>>>> org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>>>> Returning Internal Server Error response.
>>>> 2016-02-03 04:41:09,180 INFO [NiFi Web Server-264]
>>>> o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>> request:
>>>> org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>>>> Returning Internal Server Error response.
>>>> 2016-02-03 04:41:09,180 INFO [NiFi Web Server-346]
>>>> o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>> request:
>>>> org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>>>> Returning Internal Server Error response.
>>>> 2016-02-03 04:41:09,180 INFO [NiFi Web Server-367]
>>>> o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>> request:
>>>> org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
>>>> Cannot apply GET request to
>>>>
>>>
>>> http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2
>>> -
>>>> 4
>>>
>>>> e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3a
>>>> df
>>>> 8
>>>> df113 because there are currently no connected Nodes. Returning
>>> Internal
>>>> Server Error response.
>>>> 2016-02-03 04:41:10,066 INFO [NiFi Web Server-368]
>>>> o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>> request:
>>>> org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
>>>> Cannot apply GET request to
>>>> http://10.233.0.183:8080/nifi-api/controller/config because there are
>>>> currently no connected Nodes. Returning Internal Server Error response.
>>>> 2016-02-03 04:41:10,681 INFO [Process NCM Request-6]
>>>> o.a.n.c.p.impl.SocketProtocolListener Received request
>>>> 55b07d8c-a5ce-4a4f-bb59-059789153fcd from 10.233.0.180
>>>> 2016-02-03 04:41:10,683 INFO [Process NCM Request-6]
>>>> o.a.n.c.p.impl.SocketProtocolListener Finished processing request
>>>> 55b07d8c-a5ce-4a4f-bb59-059789153fcd (type=BULLETINS, length=1877
>>> bytes)
>>>> in 61 millis
>>>>
>>>>
>>>>
>>>> On 2/2/16, 8:40 PM, "Paresh Shah" <Paresh.Shah@lifelock.com
>>> <javascript:;>> wrote:
>>>>
>>>>> We have multiple cluster setup.
>>>>>
>>>>> Cluster 1:
>>>>> NCM : 10.233.0.183:8080
>>>>> Nodes: 10.233.0.156, 10.233.0.180
>>>>>
>>>>> Cluster 2:
>>>>> NCM : i-e9c63569.dev.aws.lifelock.ad
>>>>> Nodes :
>>>>> i-e9c63569.dev.aws.lifelock.ad<http://i-e9c63569.dev.aws.lifelock.ad>,
>>>>> i-e9c63569.dev.aws.lifelock.ad
>>>>>
>>>>> We were able to successfully connect the RPG from Cluster 1 to the
>>> remote
>>>>> input port. But are unable to send the data to the remote cluster.
>>> This
>>>>> means
>>>>>
>>>>> We are able to log in to the cluster(s) and see that the nodes are
>>>>> connected.
>>>>> Here¹s snippets of the logs from the cluster that we are trying to
>>> send
>>>>> the data from.
>>>>>
>>>>>
>>>>> 2016-02-03 04:30:58,565 INFO [NiFi Web Server-236]
>>>>> org.apache.nifi.web.filter.RequestLogger Attempting request for
>>>>> (anonymous) GET
>>>>> http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>>>>> ip: 10.233.0.156)
>>>>>
>>>>> 2016-02-03 04:31:06,093 INFO [NiFi Web Server-236]
>>>>> org.apache.nifi.web.filter.RequestLogger Attempting request for
>>>>> (anonymous) GET
>>>>>
>>>
>>> http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/process-gr
>>>>> o
>>>>> ups/ec38494d-b925-4afb-a0c0-2a02861ec03e/status (source ip:
>>> 172.16.2.33)
>>>>>
>>>>> 2016-02-03 04:31:06,210 INFO [NiFi Web Server-2695]
>>>>> org.apache.nifi.web.filter.RequestLogger Attempting request for
>>>>> (anonymous) GET
>>>>> http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/status
>>>>> (source ip: 172.16.2.33)
>>>>>
>>>>> 2016-02-03 04:31:06,217 INFO [NiFi Web Server-1273]
>>>>> org.apache.nifi.web.filter.RequestLogger Attempting request for
>>>>> (anonymous) GET
>>>
>>>>> http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/revision
>>>>> (source ip: 172.16.2.33)
>>>>>
>>>>> 2016-02-03 04:31:07,407 INFO [NiFi Web Server-2694]
>>>>> org.apache.nifi.web.filter.RequestLogger Attempting request for
>>>>> (anonymous) GET
>>>>> http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>>>>> ip: 10.233.0.180)
>>>>>
>>>>> 2016-02-03 04:31:07,433 INFO [NiFi Web Server-2695]
>>>>> org.apache.nifi.web.filter.RequestLogger Attempting request for
>>>>> (anonymous) GET
>>>>> http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>>>>> ip: 10.233.0.156)
>>>>>
>>>>> ________________________________
>>>>> 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.
>>>>> ________________________________
>>>>
>>>> ________________________________
>>>> 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.
>>>> ________________________________
>>>
>>> ________________________________
>>> 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.
>>> ________________________________
>>>
>
> ________________________________
> 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.
> ________________________________
Re: Unable to communicate between two Nifi clusters.
Posted by Chakrader Dewaragatla <Ch...@lifelock.com>.
Ricard - Yes, FQDN lookup works from the node.
[root@ip-10-233-0-156 logs]# telnet i-e9c63569.dev.aws.lifelock.ad 8080
Trying 10.228.68.219...
Connected to i-e9c63569.dev.aws.lifelock.ad.
Escape character is '^]'.
On 2/2/16, 11:11 PM, "Richard Miskin" <r....@gmail.com> wrote:
>It looks like you're using a fully qualified name in the node
>configuration
>but you've tested an IP address using telnet. Is
>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi correct?
>
>Richard
>
>
>On Wednesday, 3 February 2016, Chakrader Dewaragatla <
>Chakrader.Dewaragatla@lifelock.com> wrote:
>
>> On Cluster 1 salves, we notice time out connecting to Cluster 2 NCM.
>>
>> 2016-02-03 06:51:42,585 WARN [Timer-Driven Process Thread-4]
>> o.a.n.r.c.socket.EndpointConnectionPool EndpointConnectionPool[Cluster
>> URL=http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi] Unable to refresh
>> Remote Group's peers due to {}
>> java.net.ConnectException: Connection timed out
>>
>>
>>
>> Network ports/firewall seems to be ok.
>>
>> [root@ip-10-233-0-156 logs]# telnet 10.228.68.219 8080
>> Trying 10.228.68.219...
>> Connected to 10.228.68.219.
>> Escape character is '^]'.
>> ^\Connection closed by foreign host.
>>
>>
>>
>> Curl or wget works fine as well.
>>
>>
>> On 2/2/16, 8:43 PM, "Paresh Shah" <Paresh.Shah@lifelock.com
>><javascript:;>>
>> wrote:
>>
>> >More updates. Now the sending cluster reports that the nodes are
>> >disconnected.
>> >
>> >...
>> >2016-02-03 04:41:09,176 WARN [NiFi Web Server-313]
>> >o.a.n.c.manager.impl.WebClusterManager All nodes failed to process URI
>> >
>>
>>http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2
>>-
>> >4
>>
>>>e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3a
>>>df
>> >8
>> >df113. As a result, no node will be disconnected from cluster
>> >2016-02-03 04:41:09,177 INFO [NiFi Web Server-313]
>> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>request:
>> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
>>All
>> >nodes were disconnected as a result of applying request PUT
>> >
>>
>>http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2
>>-
>> >4
>>
>>>e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3a
>>>df
>> >8
>> >df113. Returning Internal Server Error response.
>> >2016-02-03 04:41:09,178 INFO [NiFi Web Server-348]
>> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>request:
>> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>> >Returning Internal Server Error response.
>> >2016-02-03 04:41:09,179 INFO [NiFi Web Server-365]
>> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>request:
>> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>> >Returning Internal Server Error response.
>> >2016-02-03 04:41:09,180 INFO [NiFi Web Server-264]
>> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>request:
>> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>> >Returning Internal Server Error response.
>> >2016-02-03 04:41:09,180 INFO [NiFi Web Server-346]
>> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>request:
>> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>> >Returning Internal Server Error response.
>> >2016-02-03 04:41:09,180 INFO [NiFi Web Server-367]
>> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>request:
>> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
>> >Cannot apply GET request to
>> >
>>
>>http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2
>>-
>> >4
>>
>>>e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3a
>>>df
>> >8
>> >df113 because there are currently no connected Nodes. Returning
>>Internal
>> >Server Error response.
>> >2016-02-03 04:41:10,066 INFO [NiFi Web Server-368]
>> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing
>>request:
>> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
>> >Cannot apply GET request to
>> >http://10.233.0.183:8080/nifi-api/controller/config because there are
>> >currently no connected Nodes. Returning Internal Server Error response.
>> >2016-02-03 04:41:10,681 INFO [Process NCM Request-6]
>> >o.a.n.c.p.impl.SocketProtocolListener Received request
>> >55b07d8c-a5ce-4a4f-bb59-059789153fcd from 10.233.0.180
>> >2016-02-03 04:41:10,683 INFO [Process NCM Request-6]
>> >o.a.n.c.p.impl.SocketProtocolListener Finished processing request
>> >55b07d8c-a5ce-4a4f-bb59-059789153fcd (type=BULLETINS, length=1877
>>bytes)
>> >in 61 millis
>> >
>> >
>> >
>> >On 2/2/16, 8:40 PM, "Paresh Shah" <Paresh.Shah@lifelock.com
>> <javascript:;>> wrote:
>> >
>> >>We have multiple cluster setup.
>> >>
>> >>Cluster 1:
>> >>NCM : 10.233.0.183:8080
>> >>Nodes: 10.233.0.156, 10.233.0.180
>> >>
>> >>Cluster 2:
>> >>NCM : i-e9c63569.dev.aws.lifelock.ad
>> >>Nodes :
>> >>i-e9c63569.dev.aws.lifelock.ad<http://i-e9c63569.dev.aws.lifelock.ad>,
>> >>i-e9c63569.dev.aws.lifelock.ad
>> >>
>> >>We were able to successfully connect the RPG from Cluster 1 to the
>>remote
>> >>input port. But are unable to send the data to the remote cluster.
>>This
>> >>means
>> >>
>> >>We are able to log in to the cluster(s) and see that the nodes are
>> >>connected.
>> >>Here¹s snippets of the logs from the cluster that we are trying to
>>send
>> >>the data from.
>> >>
>> >>
>> >>2016-02-03 04:30:58,565 INFO [NiFi Web Server-236]
>> >>org.apache.nifi.web.filter.RequestLogger Attempting request for
>> >>(anonymous) GET
>> >>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>> >>ip: 10.233.0.156)
>> >>
>> >>2016-02-03 04:31:06,093 INFO [NiFi Web Server-236]
>> >>org.apache.nifi.web.filter.RequestLogger Attempting request for
>> >>(anonymous) GET
>> >>
>>
>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/process-gr
>> >>o
>> >>ups/ec38494d-b925-4afb-a0c0-2a02861ec03e/status (source ip:
>>172.16.2.33)
>> >>
>> >>2016-02-03 04:31:06,210 INFO [NiFi Web Server-2695]
>> >>org.apache.nifi.web.filter.RequestLogger Attempting request for
>> >>(anonymous) GET
>> >>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/status
>> >>(source ip: 172.16.2.33)
>> >>
>> >>2016-02-03 04:31:06,217 INFO [NiFi Web Server-1273]
>> >>org.apache.nifi.web.filter.RequestLogger Attempting request for
>> >>(anonymous) GET
>>
>>>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/revision
>> >>(source ip: 172.16.2.33)
>> >>
>> >>2016-02-03 04:31:07,407 INFO [NiFi Web Server-2694]
>> >>org.apache.nifi.web.filter.RequestLogger Attempting request for
>> >>(anonymous) GET
>> >>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>> >>ip: 10.233.0.180)
>> >>
>> >>2016-02-03 04:31:07,433 INFO [NiFi Web Server-2695]
>> >>org.apache.nifi.web.filter.RequestLogger Attempting request for
>> >>(anonymous) GET
>> >>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>> >>ip: 10.233.0.156)
>> >>
>> >>________________________________
>> >>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.
>> >>________________________________
>> >
>> >________________________________
>> > 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.
>> >________________________________
>>
>> ________________________________
>> 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.
>> ________________________________
>>
________________________________
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.
________________________________
Re: Unable to communicate between two Nifi clusters.
Posted by Richard Miskin <r....@gmail.com>.
It looks like you're using a fully qualified name in the node configuration
but you've tested an IP address using telnet. Is
http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi correct?
Richard
On Wednesday, 3 February 2016, Chakrader Dewaragatla <
Chakrader.Dewaragatla@lifelock.com> wrote:
> On Cluster 1 salves, we notice time out connecting to Cluster 2 NCM.
>
> 2016-02-03 06:51:42,585 WARN [Timer-Driven Process Thread-4]
> o.a.n.r.c.socket.EndpointConnectionPool EndpointConnectionPool[Cluster
> URL=http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi] Unable to refresh
> Remote Group's peers due to {}
> java.net.ConnectException: Connection timed out
>
>
>
> Network ports/firewall seems to be ok.
>
> [root@ip-10-233-0-156 logs]# telnet 10.228.68.219 8080
> Trying 10.228.68.219...
> Connected to 10.228.68.219.
> Escape character is '^]'.
> ^\Connection closed by foreign host.
>
>
>
> Curl or wget works fine as well.
>
>
> On 2/2/16, 8:43 PM, "Paresh Shah" <Paresh.Shah@lifelock.com <javascript:;>>
> wrote:
>
> >More updates. Now the sending cluster reports that the nodes are
> >disconnected.
> >
> >...
> >2016-02-03 04:41:09,176 WARN [NiFi Web Server-313]
> >o.a.n.c.manager.impl.WebClusterManager All nodes failed to process URI
> >
> http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2-
> >4
> >e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3adf
> >8
> >df113. As a result, no node will be disconnected from cluster
> >2016-02-03 04:41:09,177 INFO [NiFi Web Server-313]
> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException: All
> >nodes were disconnected as a result of applying request PUT
> >
> http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2-
> >4
> >e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3adf
> >8
> >df113. Returning Internal Server Error response.
> >2016-02-03 04:41:09,178 INFO [NiFi Web Server-348]
> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
> >Returning Internal Server Error response.
> >2016-02-03 04:41:09,179 INFO [NiFi Web Server-365]
> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
> >Returning Internal Server Error response.
> >2016-02-03 04:41:09,180 INFO [NiFi Web Server-264]
> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
> >Returning Internal Server Error response.
> >2016-02-03 04:41:09,180 INFO [NiFi Web Server-346]
> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
> >Returning Internal Server Error response.
> >2016-02-03 04:41:09,180 INFO [NiFi Web Server-367]
> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
> >Cannot apply GET request to
> >
> http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2-
> >4
> >e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3adf
> >8
> >df113 because there are currently no connected Nodes. Returning Internal
> >Server Error response.
> >2016-02-03 04:41:10,066 INFO [NiFi Web Server-368]
> >o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
> >org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
> >Cannot apply GET request to
> >http://10.233.0.183:8080/nifi-api/controller/config because there are
> >currently no connected Nodes. Returning Internal Server Error response.
> >2016-02-03 04:41:10,681 INFO [Process NCM Request-6]
> >o.a.n.c.p.impl.SocketProtocolListener Received request
> >55b07d8c-a5ce-4a4f-bb59-059789153fcd from 10.233.0.180
> >2016-02-03 04:41:10,683 INFO [Process NCM Request-6]
> >o.a.n.c.p.impl.SocketProtocolListener Finished processing request
> >55b07d8c-a5ce-4a4f-bb59-059789153fcd (type=BULLETINS, length=1877 bytes)
> >in 61 millis
> >
> >
> >
> >On 2/2/16, 8:40 PM, "Paresh Shah" <Paresh.Shah@lifelock.com
> <javascript:;>> wrote:
> >
> >>We have multiple cluster setup.
> >>
> >>Cluster 1:
> >>NCM : 10.233.0.183:8080
> >>Nodes: 10.233.0.156, 10.233.0.180
> >>
> >>Cluster 2:
> >>NCM : i-e9c63569.dev.aws.lifelock.ad
> >>Nodes :
> >>i-e9c63569.dev.aws.lifelock.ad<http://i-e9c63569.dev.aws.lifelock.ad>,
> >>i-e9c63569.dev.aws.lifelock.ad
> >>
> >>We were able to successfully connect the RPG from Cluster 1 to the remote
> >>input port. But are unable to send the data to the remote cluster. This
> >>means
> >>
> >>We are able to log in to the cluster(s) and see that the nodes are
> >>connected.
> >>Here¹s snippets of the logs from the cluster that we are trying to send
> >>the data from.
> >>
> >>
> >>2016-02-03 04:30:58,565 INFO [NiFi Web Server-236]
> >>org.apache.nifi.web.filter.RequestLogger Attempting request for
> >>(anonymous) GET
> >>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
> >>ip: 10.233.0.156)
> >>
> >>2016-02-03 04:31:06,093 INFO [NiFi Web Server-236]
> >>org.apache.nifi.web.filter.RequestLogger Attempting request for
> >>(anonymous) GET
> >>
> http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/process-gr
> >>o
> >>ups/ec38494d-b925-4afb-a0c0-2a02861ec03e/status (source ip: 172.16.2.33)
> >>
> >>2016-02-03 04:31:06,210 INFO [NiFi Web Server-2695]
> >>org.apache.nifi.web.filter.RequestLogger Attempting request for
> >>(anonymous) GET
> >>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/status
> >>(source ip: 172.16.2.33)
> >>
> >>2016-02-03 04:31:06,217 INFO [NiFi Web Server-1273]
> >>org.apache.nifi.web.filter.RequestLogger Attempting request for
> >>(anonymous) GET
> >>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/revision
> >>(source ip: 172.16.2.33)
> >>
> >>2016-02-03 04:31:07,407 INFO [NiFi Web Server-2694]
> >>org.apache.nifi.web.filter.RequestLogger Attempting request for
> >>(anonymous) GET
> >>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
> >>ip: 10.233.0.180)
> >>
> >>2016-02-03 04:31:07,433 INFO [NiFi Web Server-2695]
> >>org.apache.nifi.web.filter.RequestLogger Attempting request for
> >>(anonymous) GET
> >>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
> >>ip: 10.233.0.156)
> >>
> >>________________________________
> >>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.
> >>________________________________
> >
> >________________________________
> > 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.
> >________________________________
>
> ________________________________
> 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.
> ________________________________
>
Re: Unable to communicate between two Nifi clusters.
Posted by Chakrader Dewaragatla <Ch...@lifelock.com>.
We are using 0.4.1 nifi version.
Clusters are not secured and running with plain http.
On 2/2/16, 10:56 PM, "Chakrader Dewaragatla"
<Ch...@lifelock.com> wrote:
>On Cluster 1 salves, we notice time out connecting to Cluster 2 NCM.
>
>2016-02-03 06:51:42,585 WARN [Timer-Driven Process Thread-4]
>o.a.n.r.c.socket.EndpointConnectionPool EndpointConnectionPool[Cluster
>URL=http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi] Unable to refresh
>Remote Group's peers due to {}
>java.net.ConnectException: Connection timed out
>
>
>
>Network ports/firewall seems to be ok.
>
>[root@ip-10-233-0-156 logs]# telnet 10.228.68.219 8080
>Trying 10.228.68.219...
>Connected to 10.228.68.219.
>Escape character is '^]'.
>^\Connection closed by foreign host.
>
>
>
>Curl or wget works fine as well.
>
>
>On 2/2/16, 8:43 PM, "Paresh Shah" <Pa...@lifelock.com> wrote:
>
>>More updates. Now the sending cluster reports that the nodes are
>>disconnected.
>>
>>...
>>2016-02-03 04:41:09,176 WARN [NiFi Web Server-313]
>>o.a.n.c.manager.impl.WebClusterManager All nodes failed to process URI
>>http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2
>>-
>>4
>>e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3ad
>>f
>>8
>>df113. As a result, no node will be disconnected from cluster
>>2016-02-03 04:41:09,177 INFO [NiFi Web Server-313]
>>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException: All
>>nodes were disconnected as a result of applying request PUT
>>http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2
>>-
>>4
>>e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3ad
>>f
>>8
>>df113. Returning Internal Server Error response.
>>2016-02-03 04:41:09,178 INFO [NiFi Web Server-348]
>>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>>Returning Internal Server Error response.
>>2016-02-03 04:41:09,179 INFO [NiFi Web Server-365]
>>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>>Returning Internal Server Error response.
>>2016-02-03 04:41:09,180 INFO [NiFi Web Server-264]
>>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>>Returning Internal Server Error response.
>>2016-02-03 04:41:09,180 INFO [NiFi Web Server-346]
>>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>>Returning Internal Server Error response.
>>2016-02-03 04:41:09,180 INFO [NiFi Web Server-367]
>>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
>>Cannot apply GET request to
>>http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2
>>-
>>4
>>e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3ad
>>f
>>8
>>df113 because there are currently no connected Nodes. Returning Internal
>>Server Error response.
>>2016-02-03 04:41:10,066 INFO [NiFi Web Server-368]
>>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
>>Cannot apply GET request to
>>http://10.233.0.183:8080/nifi-api/controller/config because there are
>>currently no connected Nodes. Returning Internal Server Error response.
>>2016-02-03 04:41:10,681 INFO [Process NCM Request-6]
>>o.a.n.c.p.impl.SocketProtocolListener Received request
>>55b07d8c-a5ce-4a4f-bb59-059789153fcd from 10.233.0.180
>>2016-02-03 04:41:10,683 INFO [Process NCM Request-6]
>>o.a.n.c.p.impl.SocketProtocolListener Finished processing request
>>55b07d8c-a5ce-4a4f-bb59-059789153fcd (type=BULLETINS, length=1877 bytes)
>>in 61 millis
>>
>>
>>
>>On 2/2/16, 8:40 PM, "Paresh Shah" <Pa...@lifelock.com> wrote:
>>
>>>We have multiple cluster setup.
>>>
>>>Cluster 1:
>>>NCM : 10.233.0.183:8080
>>>Nodes: 10.233.0.156, 10.233.0.180
>>>
>>>Cluster 2:
>>>NCM : i-e9c63569.dev.aws.lifelock.ad
>>>Nodes :
>>>i-e9c63569.dev.aws.lifelock.ad<http://i-e9c63569.dev.aws.lifelock.ad>,
>>>i-e9c63569.dev.aws.lifelock.ad
>>>
>>>We were able to successfully connect the RPG from Cluster 1 to the
>>>remote
>>>input port. But are unable to send the data to the remote cluster. This
>>>means
>>>
>>>We are able to log in to the cluster(s) and see that the nodes are
>>>connected.
>>>Here¹s snippets of the logs from the cluster that we are trying to send
>>>the data from.
>>>
>>>
>>>2016-02-03 04:30:58,565 INFO [NiFi Web Server-236]
>>>org.apache.nifi.web.filter.RequestLogger Attempting request for
>>>(anonymous) GET
>>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>>>ip: 10.233.0.156)
>>>
>>>2016-02-03 04:31:06,093 INFO [NiFi Web Server-236]
>>>org.apache.nifi.web.filter.RequestLogger Attempting request for
>>>(anonymous) GET
>>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/process-g
>>>r
>>>o
>>>ups/ec38494d-b925-4afb-a0c0-2a02861ec03e/status (source ip: 172.16.2.33)
>>>
>>>2016-02-03 04:31:06,210 INFO [NiFi Web Server-2695]
>>>org.apache.nifi.web.filter.RequestLogger Attempting request for
>>>(anonymous) GET
>>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/status
>>>(source ip: 172.16.2.33)
>>>
>>>2016-02-03 04:31:06,217 INFO [NiFi Web Server-1273]
>>>org.apache.nifi.web.filter.RequestLogger Attempting request for
>>>(anonymous) GET
>>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/revision
>>>(source ip: 172.16.2.33)
>>>
>>>2016-02-03 04:31:07,407 INFO [NiFi Web Server-2694]
>>>org.apache.nifi.web.filter.RequestLogger Attempting request for
>>>(anonymous) GET
>>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>>>ip: 10.233.0.180)
>>>
>>>2016-02-03 04:31:07,433 INFO [NiFi Web Server-2695]
>>>org.apache.nifi.web.filter.RequestLogger Attempting request for
>>>(anonymous) GET
>>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>>>ip: 10.233.0.156)
>>>
>>>________________________________
>>>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.
>>>________________________________
>>
>>________________________________
>> 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.
>>________________________________
>
________________________________
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.
________________________________
Re: Unable to communicate between two Nifi clusters.
Posted by Chakrader Dewaragatla <Ch...@lifelock.com>.
On Cluster 1 salves, we notice time out connecting to Cluster 2 NCM.
2016-02-03 06:51:42,585 WARN [Timer-Driven Process Thread-4]
o.a.n.r.c.socket.EndpointConnectionPool EndpointConnectionPool[Cluster
URL=http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi] Unable to refresh
Remote Group's peers due to {}
java.net.ConnectException: Connection timed out
Network ports/firewall seems to be ok.
[root@ip-10-233-0-156 logs]# telnet 10.228.68.219 8080
Trying 10.228.68.219...
Connected to 10.228.68.219.
Escape character is '^]'.
^\Connection closed by foreign host.
Curl or wget works fine as well.
On 2/2/16, 8:43 PM, "Paresh Shah" <Pa...@lifelock.com> wrote:
>More updates. Now the sending cluster reports that the nodes are
>disconnected.
>
>...
>2016-02-03 04:41:09,176 WARN [NiFi Web Server-313]
>o.a.n.c.manager.impl.WebClusterManager All nodes failed to process URI
>http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2-
>4
>e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3adf
>8
>df113. As a result, no node will be disconnected from cluster
>2016-02-03 04:41:09,177 INFO [NiFi Web Server-313]
>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException: All
>nodes were disconnected as a result of applying request PUT
>http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2-
>4
>e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3adf
>8
>df113. Returning Internal Server Error response.
>2016-02-03 04:41:09,178 INFO [NiFi Web Server-348]
>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>Returning Internal Server Error response.
>2016-02-03 04:41:09,179 INFO [NiFi Web Server-365]
>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>Returning Internal Server Error response.
>2016-02-03 04:41:09,180 INFO [NiFi Web Server-264]
>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>Returning Internal Server Error response.
>2016-02-03 04:41:09,180 INFO [NiFi Web Server-346]
>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
>Returning Internal Server Error response.
>2016-02-03 04:41:09,180 INFO [NiFi Web Server-367]
>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
>Cannot apply GET request to
>http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2-
>4
>e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3adf
>8
>df113 because there are currently no connected Nodes. Returning Internal
>Server Error response.
>2016-02-03 04:41:10,066 INFO [NiFi Web Server-368]
>o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
>org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
>Cannot apply GET request to
>http://10.233.0.183:8080/nifi-api/controller/config because there are
>currently no connected Nodes. Returning Internal Server Error response.
>2016-02-03 04:41:10,681 INFO [Process NCM Request-6]
>o.a.n.c.p.impl.SocketProtocolListener Received request
>55b07d8c-a5ce-4a4f-bb59-059789153fcd from 10.233.0.180
>2016-02-03 04:41:10,683 INFO [Process NCM Request-6]
>o.a.n.c.p.impl.SocketProtocolListener Finished processing request
>55b07d8c-a5ce-4a4f-bb59-059789153fcd (type=BULLETINS, length=1877 bytes)
>in 61 millis
>
>
>
>On 2/2/16, 8:40 PM, "Paresh Shah" <Pa...@lifelock.com> wrote:
>
>>We have multiple cluster setup.
>>
>>Cluster 1:
>>NCM : 10.233.0.183:8080
>>Nodes: 10.233.0.156, 10.233.0.180
>>
>>Cluster 2:
>>NCM : i-e9c63569.dev.aws.lifelock.ad
>>Nodes :
>>i-e9c63569.dev.aws.lifelock.ad<http://i-e9c63569.dev.aws.lifelock.ad>,
>>i-e9c63569.dev.aws.lifelock.ad
>>
>>We were able to successfully connect the RPG from Cluster 1 to the remote
>>input port. But are unable to send the data to the remote cluster. This
>>means
>>
>>We are able to log in to the cluster(s) and see that the nodes are
>>connected.
>>Here¹s snippets of the logs from the cluster that we are trying to send
>>the data from.
>>
>>
>>2016-02-03 04:30:58,565 INFO [NiFi Web Server-236]
>>org.apache.nifi.web.filter.RequestLogger Attempting request for
>>(anonymous) GET
>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>>ip: 10.233.0.156)
>>
>>2016-02-03 04:31:06,093 INFO [NiFi Web Server-236]
>>org.apache.nifi.web.filter.RequestLogger Attempting request for
>>(anonymous) GET
>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/process-gr
>>o
>>ups/ec38494d-b925-4afb-a0c0-2a02861ec03e/status (source ip: 172.16.2.33)
>>
>>2016-02-03 04:31:06,210 INFO [NiFi Web Server-2695]
>>org.apache.nifi.web.filter.RequestLogger Attempting request for
>>(anonymous) GET
>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/status
>>(source ip: 172.16.2.33)
>>
>>2016-02-03 04:31:06,217 INFO [NiFi Web Server-1273]
>>org.apache.nifi.web.filter.RequestLogger Attempting request for
>>(anonymous) GET
>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/revision
>>(source ip: 172.16.2.33)
>>
>>2016-02-03 04:31:07,407 INFO [NiFi Web Server-2694]
>>org.apache.nifi.web.filter.RequestLogger Attempting request for
>>(anonymous) GET
>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>>ip: 10.233.0.180)
>>
>>2016-02-03 04:31:07,433 INFO [NiFi Web Server-2695]
>>org.apache.nifi.web.filter.RequestLogger Attempting request for
>>(anonymous) GET
>>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>>ip: 10.233.0.156)
>>
>>________________________________
>>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.
>>________________________________
>
>________________________________
> 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.
>________________________________
________________________________
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.
________________________________
Re: Unable to communicate between two Nifi clusters.
Posted by Paresh Shah <Pa...@lifelock.com>.
More updates. Now the sending cluster reports that the nodes are
disconnected.
...
2016-02-03 04:41:09,176 WARN [NiFi Web Server-313]
o.a.n.c.manager.impl.WebClusterManager All nodes failed to process URI
http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2-4
e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3adf8
df113. As a result, no node will be disconnected from cluster
2016-02-03 04:41:09,177 INFO [NiFi Web Server-313]
o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
org.apache.nifi.cluster.manager.exception.NoConnectedNodesException: All
nodes were disconnected as a result of applying request PUT
http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2-4
e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3adf8
df113. Returning Internal Server Error response.
2016-02-03 04:41:09,178 INFO [NiFi Web Server-348]
o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
Returning Internal Server Error response.
2016-02-03 04:41:09,179 INFO [NiFi Web Server-365]
o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
Returning Internal Server Error response.
2016-02-03 04:41:09,180 INFO [NiFi Web Server-264]
o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
Returning Internal Server Error response.
2016-02-03 04:41:09,180 INFO [NiFi Web Server-346]
o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
org.apache.nifi.cluster.manager.exception.NoConnectedNodesException.
Returning Internal Server Error response.
2016-02-03 04:41:09,180 INFO [NiFi Web Server-367]
o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
Cannot apply GET request to
http://10.233.0.183:8080/nifi-api/controller/process-groups/c8236793-3ea2-4
e03-a721-f63ada78c1cd/remote-process-groups/1a8cb3c7-8705-4e11-ac03-df3adf8
df113 because there are currently no connected Nodes. Returning Internal
Server Error response.
2016-02-03 04:41:10,066 INFO [NiFi Web Server-368]
o.a.n.c.m.e.NoConnectedNodesException Cluster failed processing request:
org.apache.nifi.cluster.manager.exception.NoConnectedNodesException:
Cannot apply GET request to
http://10.233.0.183:8080/nifi-api/controller/config because there are
currently no connected Nodes. Returning Internal Server Error response.
2016-02-03 04:41:10,681 INFO [Process NCM Request-6]
o.a.n.c.p.impl.SocketProtocolListener Received request
55b07d8c-a5ce-4a4f-bb59-059789153fcd from 10.233.0.180
2016-02-03 04:41:10,683 INFO [Process NCM Request-6]
o.a.n.c.p.impl.SocketProtocolListener Finished processing request
55b07d8c-a5ce-4a4f-bb59-059789153fcd (type=BULLETINS, length=1877 bytes)
in 61 millis
On 2/2/16, 8:40 PM, "Paresh Shah" <Pa...@lifelock.com> wrote:
>We have multiple cluster setup.
>
>Cluster 1:
>NCM : 10.233.0.183:8080
>Nodes: 10.233.0.156, 10.233.0.180
>
>Cluster 2:
>NCM : i-e9c63569.dev.aws.lifelock.ad
>Nodes :
>i-e9c63569.dev.aws.lifelock.ad<http://i-e9c63569.dev.aws.lifelock.ad>,
>i-e9c63569.dev.aws.lifelock.ad
>
>We were able to successfully connect the RPG from Cluster 1 to the remote
>input port. But are unable to send the data to the remote cluster. This
>means
>
>We are able to log in to the cluster(s) and see that the nodes are
>connected.
>Here¹s snippets of the logs from the cluster that we are trying to send
>the data from.
>
>
>2016-02-03 04:30:58,565 INFO [NiFi Web Server-236]
>org.apache.nifi.web.filter.RequestLogger Attempting request for
>(anonymous) GET
>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>ip: 10.233.0.156)
>
>2016-02-03 04:31:06,093 INFO [NiFi Web Server-236]
>org.apache.nifi.web.filter.RequestLogger Attempting request for
>(anonymous) GET
>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/process-gro
>ups/ec38494d-b925-4afb-a0c0-2a02861ec03e/status (source ip: 172.16.2.33)
>
>2016-02-03 04:31:06,210 INFO [NiFi Web Server-2695]
>org.apache.nifi.web.filter.RequestLogger Attempting request for
>(anonymous) GET
>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/status
>(source ip: 172.16.2.33)
>
>2016-02-03 04:31:06,217 INFO [NiFi Web Server-1273]
>org.apache.nifi.web.filter.RequestLogger Attempting request for
>(anonymous) GET
>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller/revision
>(source ip: 172.16.2.33)
>
>2016-02-03 04:31:07,407 INFO [NiFi Web Server-2694]
>org.apache.nifi.web.filter.RequestLogger Attempting request for
>(anonymous) GET
>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>ip: 10.233.0.180)
>
>2016-02-03 04:31:07,433 INFO [NiFi Web Server-2695]
>org.apache.nifi.web.filter.RequestLogger Attempting request for
>(anonymous) GET
>http://i-e9c63569.dev.aws.lifelock.ad:8080/nifi-api/controller (source
>ip: 10.233.0.156)
>
>________________________________
>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.
>________________________________
________________________________
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.
________________________________