Re: Setting basic NiFi network problem

Yes, you need to ensure that each node in the cluster (each instance of the application) is running its web server on a unique port if they are all running on the same machine. You’ll also need to pay attention to the S2S and cluster protocol ports. Pierre Villard has written an excellent

Setting basic NiFi network problem

Okay so I know that this is certainly a duplicate post but i really need help setting this up. I have installed NiFi and compiled but I am getting stuck trying to setup the basic network. So I am thinking I am misconfiguring the ports because I am trying to build a 3 node network with just

RE: [EXT] Re: OverlappingFileLockException while restarting

Joe, Looks like there was no other process running but the actual culprit was this property " nifi.remote.input.secure=false". I set the flag back to true and everything started working again and I am really confused by this vague error, right now I am facing a different issue when I'm trying

Re: OverlappingFileLockException while restarting

most likely there is another instance of nifi still running. Check ps -ef | grep nifi. Kill that and try again. Thanks On Thu, May 25, 2017 at 12:10 PM, Karthik Kothareddy (karthikk) [CONT - Type 2] wrote: > Hello, > > I am running 1.2.0 Snapshot on a Linux instance with

OverlappingFileLockException while restarting

Hello, I am running 1.2.0 Snapshot on a Linux instance with some custom processors. I was trying to update a certificate this morning and restart the instance and I'm stuck with the "OverlappingFileLockException". The instance would not start and soon after I start it ,it will shutdown with

Re: unstable cluster

looked at a secured cluster and the send times are routinely at 100ms similar to yours. I think what i was flagging as potentially interesting is not interesting at all. On Thu, May 25, 2017 at 11:34 AM, Joe Witt wrote: > Ok. Well as a point of comparison i'm looking at

Re: unstable cluster

Ok. Well as a point of comparison i'm looking at heartbeat logs from another cluster and the times are consistently 1-3 millis for the send. Yours above show 100+ms typical with one north of 900ms. Not sure how relevant that is but something i noticed. On Thu, May 25, 2017 at 11:29 AM, Mark

Re: unstable cluster

ping shows acceptably fast response time between servers, approximately 0.100-0.150 ms On Thu, May 25, 2017 at 11:13 AM, Joe Witt wrote: > have you evaluated latency across the machines in your cluster? I ask > because 122ms is pretty long and 917ms is very long. Are

Re: unstable cluster

have you evaluated latency across the machines in your cluster? I ask because 122ms is pretty long and 917ms is very long. Are these nodes across a WAN link? On Thu, May 25, 2017 at 11:08 AM, Mark Bean wrote: > Update: now all 5 nodes, regardless of ZK server, are

Re: unstable cluster

Update: now all 5 nodes, regardless of ZK server, are indicating SUSPENDED -> RECONNECTED. On Thu, May 25, 2017 at 10:23 AM, Mark Bean wrote: > I reduced the number of embedded ZooKeeper servers on the 5-Node NiFi > Cluster from 5 to 3. This has improved the situation. I

Re: unstable cluster

I reduced the number of embedded ZooKeeper servers on the 5-Node NiFi Cluster from 5 to 3. This has improved the situation. I do not see any of the three Nodes which are also ZK servers disconnecting/reconnecting to the cluster as before. However, the two Nodes which are not running ZK continue to

Re: Not able to see the uploaded file in S3

Looks like you have checked the auto-terminate relationship and the upload fails silently. Make sure you expose the failure relationship from the PutS3 by sending it e.g. to a funnel. On Thu, May 25, 2017, 7:00 AM suman@cuddle.ai wrote: > Hi All, > > I have a simple

Not able to see the uploaded file in S3

Hi All, I have a simple flow consists of following processors. GetFile-->PutS3Object The flow is successful but not able to see the file in S3. When I checked NiFi DataProvenance of PutS3Object in details section i can see the below message. Details Auto-Terminated by failure Relationship in