[
https://issues.apache.org/jira/browse/NIFI-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002847#comment-16002847
]
ASF GitHub Bot commented on NIFI-3716:
--------------------------------------
Github user josephxsxn commented on the issue:
https://github.com/apache/nifi/pull/1747
You need to update the root nifi project pom file, and the toolkit-assembly
pom to include this otherwise it does not get packed into the toolkit
assembly. When this happens your script exists but it cant find the libs
because they didnt get properly packed into the assembly.
when running the below we can probably change the message -
```
>sh flow-analyzer.sh
Usage: java -cp <jarfile>
org.apache.nifi.toolkit.flowanalyzer.FlowAnalyzerDriver <path to
flowfile.xml.gz>
``
> Utility to calculate MAX storage required for BackPressure on a Node
> --------------------------------------------------------------------
>
> Key: NIFI-3716
> URL: https://issues.apache.org/jira/browse/NIFI-3716
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joseph Niemiec
> Assignee: Eric Ulicny
> Priority: Trivial
>
> Today there is no way to understand the max amount of data which can be
> stored in backpressure for a given flow. Personally have had users configure
> queues with impossible backpressure amounts that would definitely fill the
> disk, having an operational tool to understand if anyone has done something
> so dramatic would be helpful.
> I see this produce a report by analyzing the FlowFile.xml.gz.
> * Total Storage for all queues Backpressure
> * Average Storage of all queues Backpressure
> * Min and Max of all queues Backpressure over the entire flow.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
