[jira] [Updated] (NIFI-10974) Incorrect warning message on memory usage from MonitorMemory

["Mark Bathori (Jira)" <ji...@apache.org>]

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

Mark Bathori updated NIFI-10974:
--------------------------------
    Status: Patch Available  (was: Open)

> Incorrect warning message on memory usage from MonitorMemory
> ------------------------------------------------------------
>
>                 Key: NIFI-10974
>                 URL: https://issues.apache.org/jira/browse/NIFI-10974
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Mark Bathori
>            Assignee: Mark Bathori
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> There are certain cases when the MonitorMemory reporting task is sending incorrect warning messages on memory usage crossing the threshold.
> {+}Repro steps{+}:
>  * In the MonitorMemory reporting task, set the threshold value to low enough that the current memory usage is crossing that value.
>  * Restart NiFi while the monitoring task is still running.
>  * After the restart set the threshold to higher value above the actual memory usage.
>  * The warning messages will be still send despite the threshold is above the actual memory usage.
> The main problem is that the *isCollectionUsageThresholdExceeded()* method call on *MemoryPoolMXBean* have a *gcSensor* registered at the VM that's 'on' attribute will get stuck on 'true' value. This will cause the method to always return with exceeded. The sensor will get reseted on the next garbage collection but until that it will send false messages.



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