We are experiencing this issue as well. We just upgraded from Nifi 1.11.4 to
1.13.2, and are running in to this issue where many of our high-usage Nifi
instances are just hanging. For example, we have a 7 node cluster that has
flowfiles stuck in queues and not moving. We noticed that on 3 of
en
unsuccessful, signaling that it is nearly full or the objects are ill suited
for tighter packing.
* size or number of entries is greater than or equal to their respective,
optionally, specified maximum
Let us know if you have any other questions!
On Thu, Nov 19, 2015 at 8:09 AM, Elli Schwa
Hello,
I'm a bit confused about the relationship of certain properties of the
MergeContent processor. Specifically, how do the properties min entries, max
entries, max bin age, max number of bins interact? If the MergeContent
processor receives the min number of entries, does it merge without
it there and what it is blocked on.
Thanks
Joe
On Fri, Nov 6, 2015 at 11:25 AM, Elli Schwarz <eliezer_schw...@yahoo.com> wrote:
> I had a queue that built up overnight with several thousand flowfiles. The
> queue was pointing to a RouteOnAttribute processor, which
Hello,
We have a nifi flow with many custom processors (and many processor groups). We
suspect that one or more processors are eating up CPU usage, so we're wondering
if there's an easy way to tell which processor has a heavy load on the CPU.
There are tables to see processors in order of
