geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-154) HDFS region with HeapLRU reports LowMemoryExceptions even when the region size is less then the eviction threshold
Date Thu, 06 Aug 2015 09:00:10 GMT

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

ASF subversion and git services commented on GEODE-154:
-------------------------------------------------------

Commit c575983f14c5417cd631f0d144f514d4c6cf79c1 in incubator-geode's branch refs/heads/develop
from Namrata Thanvi
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=c575983 ]

    Fix GEODE-154: HDFS region with HeapLRU reports LowMemoryExceptions
    even when region size is less then the eviction threshold

    - calling setUsageThreshold() on MemoryPoolMXBean resulted in
    it reporting incorrect memory usage causing temporary spikes.
    Since we already set CollectionThreshold at 1 byte and also have a
    stat and heap poller thread, we now skip setting the usage threshold.


> HDFS region with HeapLRU reports LowMemoryExceptions even when the region size is less
then the eviction threshold
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-154
>                 URL: https://issues.apache.org/jira/browse/GEODE-154
>             Project: Geode
>          Issue Type: Bug
>          Components: hdfs
>    Affects Versions: 1.0.0-incubating
>            Reporter: Namrata
>            Assignee: Namrata
>             Fix For: 1.0.0-incubating
>
>
> I discovered this while writing a test for GEODE-10.  When a HDFS region with eviction
is configured then it reports LowMemoryException even when we are not even close to the  eviction
threshold. With the stat It looks like that at the LowMemoryException was reported only with
20% of the heap usage.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message