Edward, Documentation on this feature may be found here: https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#settings
Warm regards, Jim Williams ________________________________ From: Edward Armes <edward.ar...@gmail.com> Sent: Thursday, July 4, 2019 5:54 AM To: users@nifi.apache.org Subject: Re: DistributeLoad across a NiFi cluster Hi Andrew, Is this functionality documented anywhere do you know? As I've had a quick look through the documentation and I haven't seen this. Edward On Tue, Jul 2, 2019 at 5:33 PM James McMahon <jsmcmah...@gmail.com<mailto:jsmcmah...@gmail.com>> wrote: Excellent - thanks very much Andrew. This is my first crack at working with a clustered configuration, and I guess that shows by my question. Outstanding - thanks again. On Tue, Jul 2, 2019 at 12:29 PM Andrew Grande <apere...@gmail.com<mailto:apere...@gmail.com>> wrote: Jim, There's a better solution in NiFi. Right click on the connection between ListFile and FetchFile and select a cluster distribution strategy in options. That's it :) Andrew On Tue, Jul 2, 2019, 7:37 AM James McMahon <jsmcmah...@gmail.com<mailto:jsmcmah...@gmail.com>> wrote: We would like to employ a DistributeLoad processor, restricted to run on the primary node of our cluster. Is there a recommended approach employed to efficiently distribute across nodes in the cluster? As I understand it, and using a FetchFile running in "all nodes" as the first processor following the DistributeLoad, I can have it distribute by round robin, next available, or load distribution service. Can anyone provide a link to an example that employs the load distribution service? Is that the recommended distribution approach when running in clustered mode? I am interested in maintaining load balance across my cluster nodes when running at high flowfile volumes. Flow files will vary greatly in contents, so I'd like to design with an approach that helps me balance processing distribution. Thanks very much in advance. -Jim Confidentiality Notice | This email and any included attachments may be privileged, confidential and/or otherwise protected from disclosure. Access to this email by anyone other than the intended recipient is unauthorized. If you believe you have received this email in error, please contact the sender immediately and delete all copies. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
