Re: Oversized queue between process groups

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

Nifi Cluster Untrusted Proxy Error

Hi All, I am receiving an error while setting up a 2 node cluster (external zk) using Google Auth [OpenID connect] *Insufficient Permissions* *Untrusted proxy CN=*.dummy.com , OU=NIFI* We have used nifi toolkit to generate the certificates: ./bin/tls-toolkit.sh standalone -n

Re: Oversized queue between process groups

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

Still have Network traffic after stopped the CaptureChangeMySQL processor.

Using CaptureChangeMySQL to parse binlog from mysql server. Surely there will be network traffic transmission from the MySQL server to NiFi Server. But after I stop the CaptureChangeMySQL processor, why the network traffic transmission still exists? Thanks, Lei

Still have Network traffic after stopped the CaptureChangeMySQL processor.

Using CaptureChangeMySQL to parse binlog from mysql server. Surely there will be network traffic transmission from the MySQL server to NiFi Server. But after I stop the CaptureChangeMySQL processor, why the network traffic transmission still exists? Thanks, Lei

Re: Oversized queue between process groups

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

Re: Oversized queue between process groups

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

Re: Oversized queue between process groups

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

Re: Oversized queue between process groups

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