You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2024/07/06 15:32:00 UTC

[jira] [Commented] (NIFI-13420) /system-diagnostics rest call can return a negative number for nonHeapUtilization

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

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

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

NIFI-13420 Maintain consistent maxNonHeapBytes for clustered diagnostics

- The merged value of maxNonHeapBytes should be -1 when at least one node has that value

This closes #9055

Signed-off-by: David Handermann <ex...@apache.org>


> /system-diagnostics rest call can return a negative number for nonHeapUtilization
> ---------------------------------------------------------------------------------
>
>                 Key: NIFI-13420
>                 URL: https://issues.apache.org/jira/browse/NIFI-13420
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.25.0, 2.0.0-M2
>            Reporter: Nissim Shiman
>            Assignee: Nissim Shiman
>            Priority: Major
>             Fix For: 2.0.0-M4
>
>
> This is seen more clearly in clusters as single node nifis don't always return this in results.
> Can also be seen in 1.x ui, and old 2.0.0 ui (for clusters) 
> GlobalMenu -> Summary -> system diagnostics -> JVM -> Non Heap (with percentage next to it - this is the number that could be negative)
>  



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