[ 
https://issues.apache.org/jira/browse/NIFI-13031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863497#comment-17863497
 ] 

ASF subversion and git services commented on NIFI-13031:
--------------------------------------------------------

Commit b82e3d20b65198b926d7a7b5a835591b3e2d8ca7 in nifi's branch 
refs/heads/support/nifi-1.x from Nissim Shiman
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b82e3d20b6 ]

NIFI-13031 Changed PG StatusSnapshotDTO to use cloned copy for status

This closes #9054

Signed-off-by: David Handermann <[email protected]>


> /flow/process-groups/{id}/status rest api call will return aggregate metrics 
> for connections for one of the nodes, even when nodewise query parameter is 
> set to true
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-13031
>                 URL: https://issues.apache.org/jira/browse/NIFI-13031
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.24.0, 2.0.0-M2, 2.0.0-M3
>            Reporter: Nissim Shiman
>            Assignee: Nissim Shiman
>            Priority: Major
>              Labels: backport-needed
>             Fix For: 2.0.0-M4
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The rest api call:
> /flow/process-groups/\{id}/status (with nodewise set to true) 
> will return aggregate metrics for connections found in the process group as 
> well as nodewise metrics for those connections as well.
> One of the nodewise connections will be the same as the aggregate (i.e. 
> instead of just reporting the metrics for the connection on that node, it 
> will report the metrics across all nodes for that connection). The other 
> nodewise connections will report what the connection status is for that node.
> Behavior should be modified so all nodewise connection reporting is just for 
> that node.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to