We had to greatly enlarge the amount of RAM (up 48GB) in order to handle large
files in our dataflows (> 10MB). Our prod boxes have 128GB RAM. Our flows tend
to surge wildly in velocity and size; we can get 28GB of files across the five
node cluster at times. We’ve locked up the cluster at 18
What is the use case for implementing "Run Schedule" on a processor? We have
some JMS queue readers on a 5-node cluster that have been set to a Run schedule
of 125 ms with 2 concurrent tasks. Every so often our volume jumps from a
1,000-message-average per 5 minute period to 5,000. Status his
The approach we use for disaster recovery might be a start.
* nifi (user) has a cron job that runs BASH script on PROD server node
which copies the flow.xml.gz file to be used on another cluster to a temp
folder.
* The script decrypts the current passwords/properties in flow.xml.gz
We had this issue when NiFi flows were blocked and lots of content and flowfile
data was on disk and in RAM. We got around it by temporarily setting NiFi
JVMs to more RAM to allow the glut of content to pass and then lowering the JVM
RAM back to normal so that garbage collection can occur.
In
