[
https://issues.apache.org/jira/browse/NIFI-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064017#comment-16064017
]
ASF GitHub Bot commented on NIFI-3716:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1747
Ran `contrib-check` and all tests pass. +1, merging. I made slight
modifications to improve the `help` handling and fix some terminology
(*flowfile* -> *flow* when referring to the actual file that defines the flow
(`flow.xml.gz`) vs. a *flowfile* data object).
> 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.4.14#64029)
