HI Adam, Can you provide some more detail about what your NiFi flow is like? Are you using custom processors? I regularly use NiFi with the default bootstrap settings without issue, but if you're bringing lots of data into memory, have lots of flowfiles being processed concurrently, etc, memory usage can ramp up. Flow design can have quite a bit of impact on how much ram you need allocated to the JVM to avoid OOMEs.
On Wed, Aug 30, 2017 at 3:15 PM Adam Lamar <adamond...@gmail.com> wrote: > Hi everybody, > > I recently started up a new cloud Linux instance with 1GB of ram to do > some quick tasks in NiFi. I noticed NiFi kept dying without much > information in the logs - it just seemed to stop during startup. > > Eventually I realized the system was running out of memory and OOM killing > the process, hence the lack of information in the NiFi logs. Empirically > version 1.3.0 needs about 1.1GB of RAM to start, and my flow caused an > additional 200MB of ram usage. > > Are there any recommendations to get NiFi running with a lighter > footprint? I noted the default 512MB heap limits in the bootstrap config > (which I didn't change) so I'm guessing the ram usage is related to NiFi's > plethora of processors. > > Cheers, > Adam >
