Good question Mark. To clarify, another nifi cluster has an RPG on their
canvas (I believe they have 1.6.0 as well) with our cluster's URL, while we
have a Root input port. What I meant by "when we add receiving
Site-to-Site traffic to the mix", I just mean when they start sending to
our
Joe G,
Also, to clarify, when you say "when we add receiving Site-to-Site traffic to
the mix, the CPU spikes to the point that the nodes can't talk to each other,
resulting in the inability to view or modify the flow in the console"
what exactly does "when we add receiving Site-to-stie traffic
Yep what Mike points to is exactly what I was thinking of. Since
you're on 1.6.0 then probably the issue is something else. 1.6
included an updated jersey client or something related to that. Its
performance was really bad for our case. In 1.7.0 it was replaced
with an implementation
When I read this I thought of NIFI-4598 [1] and this may be what Joe
remembers, too. If your site-to-site clients are older than 1.5.0, then
maybe this is a factor?
[1] - https://issues.apache.org/jira/browse/NIFI-4598
-- Mike
On Fri, Aug 10, 2018 at 4:43 PM Joe Witt wrote:
> Joe G
>
> I do
Joe G
I do recall there were some fixes and improvements related to
clustering performance/thread pooling/ as it relates to site to site.
I dont recall precisely which version they went into but i'd strongly
recommend trying the latest release if you're able.
Thanks
On Fri, Aug 10, 2018 at 4:13
Whats the OS you are running on? What kind of systems? Memory stats,
network stats, JVM stats etc. How much data coming through?
On 10 August 2018 at 16:06, Joe Gresock wrote:
> Any nifi developers on this list that have any suggestions?
>
> On Wed, Aug 8, 2018 at 7:38 AM Joe Gresock wrote:
>
Any nifi developers on this list that have any suggestions?
On Wed, Aug 8, 2018 at 7:38 AM Joe Gresock wrote:
> I am running a 7-node NiFi 1.6.0 cluster that performs fairly well when
> it's simply processing its own data (putting records in Elasticsearch,
> MongoDB, running transforms, etc.).
