[
https://issues.apache.org/jira/browse/GEODE-6304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols closed GEODE-6304.
-------------------------------
> Heap memory monitor tolerance counter not properly reset
> --------------------------------------------------------
>
> Key: GEODE-6304
> URL: https://issues.apache.org/jira/browse/GEODE-6304
> Project: Geode
> Issue Type: Bug
> Components: configuration, eviction, regions
> Reporter: Ryan McMahon
> Assignee: Ryan McMahon
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The tolerance counter which determines whether a state change should actually
> be honored is not properly being reset when non-consecutive EVICTION or
> CRITICAL events are received. The purpose of this counter is to tolerate a
> configurable number of _consecutive_ "bad readings" of used bytes from the
> JVM, and was originally introduced for JRockit. However, it has been
> observed that bad readings are also possible in certain versions of Oracle
> JVM and possibly others.
> When the HeapMemoryMonitor was last refactored, a regression was introduced
> where the tolerance counter was not reset between non-consecutive EVICTION or
> CRITICAL events. This could cause an erroneous change of state if several
> non-consecutive events were received over some period of time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
