@Timothy Spann NiFi is not coming up or the NiFi UI can't be accessed? Is NiFi actually shutting back down after you start it? I suggest you try setting the following property to false in the nifi.properties file and restart your NiFi to see fi you can then access your UI to remove the problematic components: nifi.flowcontroller.autoResumeState=false If using Ambari to manage your NiFi, uncheck the box: Thanks, Matt ... View more

@Sonny Heer The HDP stack does not include NiFi. HDF is an entirely different software stack managed by its own Ambari and is installed on its own hardware. There are some post out there that will walk you through manually adding the NiFi service to an existing HDP stack; however, doing so breaks the upgradeability of your HDP stack. Here is an example of that: https://github.com/abajwa-hw/ambari-nifi-service *** Pay special attention to the "Limitations" noted on the above link. At some point in the future there will be an Ambari platform that can be used to install both HDP and HDF stack services that will still support the upgradeability, but that is not here yet and I don't know hen that will happen. Thank you, Matt ... View more

@Varun R The ReplaceText processor has two Evaluation Modes (Line-by-Line and Entire text). Entire Text is the default which reads the entire contents of your FLowFile in to NIFI's JVM heap memory for evaluation. With such a large file this strategy is not ideal and could lead to out of memory conditions for your NiFi. If the content of your FlowFile is multiple lines, you could switch to using the Line-by-Line evaluation mode which will result in less heap memory usage but ultimately the same resulting modified content in the outgoing FlowFile. So you might want to try a ReplaceText processor configuration like the following: Thanks, Matt ... View more