[jira] [Commented] (NIFI-8481) NIFI should display some warnings/errors when (a) all timer driven threads are blocked (b) Content Repository at 100%
[ https://issues.apache.org/jira/browse/NIFI-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430665#comment-17430665 ] Eric Detwiler commented on NIFI-8481: - Thumbs up. > NIFI should display some warnings/errors when (a) all timer driven threads > are blocked (b) Content Repository at 100% > - > > Key: NIFI-8481 > URL: https://issues.apache.org/jira/browse/NIFI-8481 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.13.2 >Reporter: Eric Detwiler >Priority: Minor > > We experienced an issue with NIFI where there were > 1) No errors/warnings in the log file (however, we did see INFO messages) > 2) No Errors on the UI > 3) All TimerDriven Threads were occupied (Stack dump revealed they were > waiting to write to the archive) > 4) Files sitting on disk when GetFile should have been processing > Basically NIFI was completely locked up waiting for space in the archive > content repository to be cleared out. But was not obvious since disk usage > was extremely high. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-8482) dump-nifi.bat should take a parameter for the file to dump to.
Eric Detwiler created NIFI-8482: --- Summary: dump-nifi.bat should take a parameter for the file to dump to. Key: NIFI-8482 URL: https://issues.apache.org/jira/browse/NIFI-8482 Project: Apache NiFi Issue Type: Improvement Affects Versions: 1.13.2 Environment: Windows Server 2019 Reporter: Eric Detwiler dump-nifi.bat should take a parameter for the file to dump to. Would be useful. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-8481) NIFI should display some warnings/errors when (a) all timer driven threads are blocked (b) Content Repository at 100%
Eric Detwiler created NIFI-8481: --- Summary: NIFI should display some warnings/errors when (a) all timer driven threads are blocked (b) Content Repository at 100% Key: NIFI-8481 URL: https://issues.apache.org/jira/browse/NIFI-8481 Project: Apache NiFi Issue Type: Improvement Components: Core UI Affects Versions: 1.13.2 Reporter: Eric Detwiler We experienced an issue with NIFI where there were 1) No errors/warnings in the log file (however, we did see INFO messages) 2) No Errors on the UI 3) All TimerDriven Threads were occupied (Stack dump revealed they were waiting to write to the archive) 4) Files sitting on disk when GetFile should have been processing Basically NIFI was completely locked up waiting for space in the archive content repository to be cleared out. But was not obvious since disk usage was extremely high. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-8480) nifi.properties should contain comments on how to set up for recommended enterprise settings (disks, directories, sizes)
Eric Detwiler created NIFI-8480: --- Summary: nifi.properties should contain comments on how to set up for recommended enterprise settings (disks, directories, sizes) Key: NIFI-8480 URL: https://issues.apache.org/jira/browse/NIFI-8480 Project: Apache NiFi Issue Type: Improvement Components: Configuration Management Affects Versions: 1.13.2 Reporter: Eric Detwiler One of of the most endearing aspects of nifi is you can download it and start it up in seconds. However, as we all know, the nifi.properties file needs to be significantly changed if you want to run in in an enterprise environment. It would take very little to add in the comments of the nifi.properties file a commented out section for each setting on what the enterprise recommendations are for each setting if you are actually running it in a enterprise environment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-8479) UI Placement of System Diagnostics needs improvement
Eric Detwiler created NIFI-8479: --- Summary: UI Placement of System Diagnostics needs improvement Key: NIFI-8479 URL: https://issues.apache.org/jira/browse/NIFI-8479 Project: Apache NiFi Issue Type: Improvement Components: Core UI Affects Versions: 1.13.2 Reporter: Eric Detwiler System Diagnostics is too hard to find and should be located in hamburger menu or as a tab in Summary. It is almost invisible in its current location in the bottom right of the Summary section. The interface provides key system information that should be readily accessible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-8401) o.apache.nifi.controller.FlowController Failed to capture component stats for Stats History on Windows Systems
[ https://issues.apache.org/jira/browse/NIFI-8401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17317172#comment-17317172 ] Eric Detwiler commented on NIFI-8401: - Thanks Nadeem. > o.apache.nifi.controller.FlowController Failed to capture component stats for > Stats History on Windows Systems > -- > > Key: NIFI-8401 > URL: https://issues.apache.org/jira/browse/NIFI-8401 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 1.13.2 > Environment: Windows 10 > Windows Server 2019 >Reporter: Eric Detwiler >Priority: Major > > 1.13.2 on Windows systems does not capture stats for Stats History by > default. Error log below: > Also located issue mentioned in post from March 2021. > https://community.cloudera.com/t5/Support-Questions/ERROR-FlowController-Failed-to-capture-component-stats-for/td-p/312486 > Status History as a result does not function. > > 2021-04-02 07:56:00,013 INFO [pool-20-thread-1] > o.a.n.c.r.WriteAheadFlowFileRepository Initiating checkpoint of FlowFile > Repository > 2021-04-02 07:56:00,014 INFO [pool-20-thread-1] > o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile > Repository with 0 records in 0 milliseconds > 2021-04-02 07:56:17,311 ERROR [Timer-Driven Process Thread-7] > o.apache.nifi.controller.FlowController Failed to capture component stats for > Stats History > java.lang.NullPointerException: null > at > org.apache.nifi.diagnostics.SystemDiagnostics.getOpenFileHandles(SystemDiagnostics.java:224) > at > org.apache.nifi.controller.FlowController.getNodeStatusSnapshot(FlowController.java:3011) > at > org.apache.nifi.controller.FlowController.access$400(FlowController.java:230) > at org.apache.nifi.controller.FlowController$2.run(FlowController.java:697) > at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-8401) o.apache.nifi.controller.FlowController Failed to capture component stats for Stats History on Windows Systems
Eric Detwiler created NIFI-8401: --- Summary: o.apache.nifi.controller.FlowController Failed to capture component stats for Stats History on Windows Systems Key: NIFI-8401 URL: https://issues.apache.org/jira/browse/NIFI-8401 Project: Apache NiFi Issue Type: Bug Components: Configuration Affects Versions: 1.13.2 Environment: Windows 10 Windows Server 2019 Reporter: Eric Detwiler 1.13.2 on Windows systems does not capture stats for Stats History by default. Error log below: Also located issue mentioned in post from March 2021. https://community.cloudera.com/t5/Support-Questions/ERROR-FlowController-Failed-to-capture-component-stats-for/td-p/312486 Status History as a result does not function. 2021-04-02 07:56:00,013 INFO [pool-20-thread-1] o.a.n.c.r.WriteAheadFlowFileRepository Initiating checkpoint of FlowFile Repository 2021-04-02 07:56:00,014 INFO [pool-20-thread-1] o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile Repository with 0 records in 0 milliseconds 2021-04-02 07:56:17,311 ERROR [Timer-Driven Process Thread-7] o.apache.nifi.controller.FlowController Failed to capture component stats for Stats History java.lang.NullPointerException: null at org.apache.nifi.diagnostics.SystemDiagnostics.getOpenFileHandles(SystemDiagnostics.java:224) at org.apache.nifi.controller.FlowController.getNodeStatusSnapshot(FlowController.java:3011) at org.apache.nifi.controller.FlowController.access$400(FlowController.java:230) at org.apache.nifi.controller.FlowController$2.run(FlowController.java:697) at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v8.3.4#803005)
