[
https://issues.apache.org/jira/browse/NIFI-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17499701#comment-17499701
]
ASF subversion and git services commented on NIFI-9400:
-------------------------------------------------------
Commit 0d0912d34b7d2fb9415ad6ffb782edd32b57eb22 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0d0912d ]
NIFI-9400: Ensure that we always use the CollectionUsage metrics in the mbeans
instead of the Usage metrics.
Signed-off-by: Joe Gresock <[email protected]>
This closes #5798.
> MonitorMemory reports based on incorrect values
> -----------------------------------------------
>
> Key: NIFI-9400
> URL: https://issues.apache.org/jira/browse/NIFI-9400
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.16.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The MonitorMemory reporting task is intended to report when heap is becoming
> exhausted by comparing the amount of heap used immediately after the most
> recent garbage collection to the configured threshold. It appears that this
> was broken in NIFI-1690, in which the code was changed to use
> {{MemoryPoolMXBean.getUsage()}} instead of
> {{MemoryPoolMXBean.getCollectionUsage()}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
