[
https://issues.apache.org/jira/browse/NIFI-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Clarke updated NIFI-1299:
---------------------------------
Attachment: Screen Shot 2015-12-17 at 12.35.03 PM.png
so the input for zone C is stopped due to back pressure on the receiving side.
Back pressure on the connection into Zone C RPG is also stopped because of
backpressure. So no bulletins are being created any longer on the Zone C RPG
but by looking at the zone C RPG, it looks like data is still going.
Different DFMs build different stove pipes to send data to different input
ports on the same NiFi target.
This becomes more of an issue when we add access control to the process group
level. DFM might not be able to see all the RPGs that are producing these stats.
> Multiple identical RPGs on a single NiFI share stats which can result in user
> confusion.
> ----------------------------------------------------------------------------------------
>
> Key: NIFI-1299
> URL: https://issues.apache.org/jira/browse/NIFI-1299
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 0.4.0
> Reporter: Matthew Clarke
> Priority: Minor
> Attachments: Screen Shot 2015-12-17 at 12.35.03 PM.png
>
>
> If DFMs have multiple RPGs on a single NiFi instance all configured to talk
> to the same destination NiFi, the stats displayed on that RPG are reflective
> of the total for everyone of those RPGs. It can be confusing to the users.
> For example, DFMs may have each RPG sending to a different input port, but
> "sent" number on each is the same and is larger then what was actually sent
> by just one RPG.
> Let say backpressure has stopped one of the target input ports. While no data
> may be going out via the RPG tied to that input port, the sent number still
> grows because of the other RPGs on the graph. A problem can be come masked.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
