One of my colleagues ran into a similar situation, and all that was required to fix it was to make ReplaceText work line by line. When you do that, you shouldn't run into any issues.
On Thu, Dec 3, 2020 at 1:04 PM jgunvaldson <jgunvald...@cox.net> wrote: > > Just looking for an opinion > > Knowing (for one example) that ReplaceText Processor can be very memory > intensive with large files - we are finding it more and more common to wake > up to an Out of Memory error like the following > > 2020-12-03 15:07:21,748ZUTC ERROR [Timer-Driven Process Thread-31] > o.a.nifi.processors.standard.ReplaceText > ReplaceText[id=352afe80-4195-3f56-8798-aaf8be160581] > ReplaceText[id=352afe80-4195-3f56-8798-aaf8be160581] failed to process > session due to java.lang.OutOfMemoryError: Java heap space; Processor > Administratively Yielded for 1 sec: java.lang.OutOfMemoryError: Java heap > space > java.lang.OutOfMemoryError: Java heap space > at > org.apache.nifi.processors.standard.ReplaceText.onTrigger(ReplaceText.java:255) > at > org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27) > at > org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1162) > > > My question is this. Knowing that "When an OOME occurs in a JVM this can > cause the JVM to skip instructions. Skipping instructions can compromise the > integrity of the JVM memory without displaying errors. You can't always tell > from the outside if a JVM has compromised memory, the only safe thing to do > is restart the JVM.” > > And in this case “Restart NIFI” > > Is that “our collective” understanding also, that a Restart of NIFI is > mandatory - or optional? > > Thanks > > John >
