You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Gregory Chase (JIRA)" <ji...@apache.org> on 2016/12/05 14:14:58 UTC
[jira] [Created] (GEODE-2181) I'm evaluating geode for our product.
I started wi...
Gregory Chase created GEODE-2181:
------------------------------------
Summary: I'm evaluating geode for our product. I started wi...
Key: GEODE-2181
URL: https://issues.apache.org/jira/browse/GEODE-2181
Project: Geode
Issue Type: Improvement
Reporter: Gregory Chase
I'm evaluating geode for our product. I started with a simple test to check the behavior of geode on low-mem:
- launch a locator and a single server with initial-heap==max-heap==4GB, critical-heap-percentage=90%, eviction-heap-percentage=80%
- I see that gfsh passes in addition the following jvm params to server: -Xms4000m -Xmx4000m -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=60
- create a partitioned region - run client which connects to locator and get the region as PROXY (i.e. no local cache)
- the client fills the server with elements until it gets ServerOperationException due to low memory (as expected)
- now, I remove all elements from the region and try run the client again - the client fails on the first put operation (although server is empty!)
My question is: why doesn't the GC collect removed items (I see on server status that currentHeapSize=3151MB, maximumHeapSize=3866)?. I'm expecting to be able to put data in the server if its empty...
Thanks.
*Reporter*: Assaf
*E-mail*: [mailto:assaf_waizman@amat.com]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)