Performance

Java heap space can become a problem with some configurations (like Colleague by Ellucian integration) due to the use of a jar file. It is recommended that Java Heap is changed.

Recommendation: Change the Java Heap Size From 512GB to 4GB

For more information: https://community.hortonworks.com/articles/85234/how-to-address-jvm-outofmemory-errors-in-nifi.html

Monitoring

On Windows, the size of the applog can continue to grow and not roll over. This could take up available disk space and make it impossible to get data provenance in processors. To ensure rolling logs are enabled for Windows, 

It is possible that Windows locking mechanism restricts the original file to be renamed(Check http://dev.eclipse.org/mhonarc/lists/jetty-users/msg03222.html for details).

You can omit the file property in logback.xml, and then the active log file will be computed a new for each period based on the value of fileNamePattern. A working rollingpolicy for a NiFi node on Windows is as follows:

  1. <appender name="APP_FILE">
  2. <!-- <file>${org.apache.nifi.bootstrap.config.log.dir}/nifi-app.log</file> -->
  3. <rollingPolicy>
  4. <!--
  5. For daily rollover, use 'app_%d.log'.
  6. For hourly rollover, use 'app_%d{yyyy-MM-dd_HH}.log'.
  7. To GZIP rolled files, replace '.log' with '.log.gz'.
  8. To ZIP rolled files, replace '.log' with '.log.zip'.
  9. -->
  10. <fileNamePattern>${org.apache.nifi.bootstrap.config.log.dir}/nifi-app_%d{yyyy-MM-dd_HH}.%i.log</fileNamePattern>
  11. <timeBasedFileNamingAndTriggeringPolicy>
  12. <maxFileSize>100MB</maxFileSize>
  13. </timeBasedFileNamingAndTriggeringPolicy>
  14. <!-- keep 30 log files worth of history -->
  15. <maxHistory>30</maxHistory>
  16. </rollingPolicy>

Ref: https://logback.qos.ch/manual/appenders.html

Source: https://community.hortonworks.com/questions/109473/nifi-120-on-windows-2012-server-is-not-rolling-ove.html