I checked the logs that I can find but nothing useful, most of it is gone
because the drive was full of previous logs from it generating errors about
it not being able to write or update any files. The logs are all gone now
as part of the recovery process removed all the logs. What I do notice
Jeremy,
Thanks for the details & history - I am indeed interested :) Do you see any
errors in the logs? Particularly around a failure to update the FlowFile
Repository? I am now thinking that you may be running into NIFI-5997 [1]. This
appears to have affected at least all 1.x versions prior
Thanks for your reply Mark.
The flow was in sync between nodes, no one edited it as it was started from a
Docker image and left running. It was running about a month. A restart didn't
clear the queue. Only 1 node had an issue the others where clear. The flow file
repository swap directory was
Jeremy,
I'm not sure of any bugs off the top of my head that would necessarily cause
this, but version 1.6.0 is getting fairly old, so there may well be something
that I've forgotten about. That being said, there are two "types of bugs" that
I think are most probable here: (1) There isn't
Yes there is one but not near the output port of the split json processor it's
shortly after the input port of a child PG. The output is actually connected to
3 child PGs and each of those has an update attribute processor on their output
port. The other PG input port on the left is connected
Can you show what is happening inside the first process group? Is there a
SplitText processor with line count of 1?
On Fri, Aug 30, 2019 at 4:21 AM Jeremy Pemberton-Pigott <
fuzzych...@gmail.com> wrote:
> Hi Pierre,
>
> I'm using Nifi version 1.6.0.
>
> 04/03/2018 08:16:22 UTC
>
> Tagged
Hi Pierre,
I'm using Nifi version 1.6.0.
04/03/2018 08:16:22 UTC
Tagged nifi-1.6.0-RC3
>From 7c0ee01 on branch NIFI-4995-RC3
FlowFile expiration = 0
Back pressure object threshold = 2
Back pressure data size threshold = 1GB
The connection is just from the output port of 1 PG to the input
Hi Jeremy,
It seems very weird that you get 200M flow files in a relationship that
should have backpressure set at 20k flow files. While backpressure is not a
hard limit you should not get to such numbers. Can you give us more
details? What version of NiFi are you using? What's the configuration
