You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Jeremy Dyer (JIRA)" <ji...@apache.org> on 2016/04/22 18:45:13 UTC

[jira] [Created] (NIFI-1805) Expose BackPressure status in ConnectionStatus for ReportingTask access

Jeremy Dyer created NIFI-1805:
---------------------------------

             Summary: Expose BackPressure status in ConnectionStatus for ReportingTask access
                 Key: NIFI-1805
                 URL: https://issues.apache.org/jira/browse/NIFI-1805
             Project: Apache NiFi
          Issue Type: Improvement
            Reporter: Jeremy Dyer


It is currently not possible to determine if a connection within a workflow is experiencing backpressure. While metrics are provided in the ConnectionStatus object around objectsQueued and bytesQueued this alone isn't enough to determine if any user defined backpressure is being applied. The idea is to make that information about the backpressure available inside the existing ConnectionStatus so that custom ReportingTasks can look for things like slow connections and alert appropriately. 

Mark Payne nifi dev list email excerpt - "It should be relatively easy. In FlowController, we would have to update getGroupStatus() to set the values on ConnectionStatus
and of course update ConnectionStatus to have getters & setters for the new values. That should be about it, I think."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)