[ 
https://issues.apache.org/jira/browse/NIFI-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Payne updated NIFI-9400:
-----------------------------
    Fix Version/s: 1.16.0
         Assignee: Mark Payne
           Status: Patch Available  (was: Open)

> 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)

Reply via email to