geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Smith (JIRA)" <>
Subject [jira] [Commented] (GEODE-2181) I'm evaluating geode for our product. I started wi...
Date Thu, 28 Sep 2017 22:09:00 GMT


Dan Smith commented on GEODE-2181:

Are you eventually able to put again? GC does happen instantly, so some time has to elapse
before garbage collection happens and geode detects that there is now free memory.

Also, how are you removing the elements? I'm not sure, but Region.clear on the client side
might just clear the client side cache.

> I'm evaluating geode for our product. I started wi...
> -----------------------------------------------------
>                 Key: GEODE-2181
>                 URL:
>             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%,
> - 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*: []

This message was sent by Atlassian JIRA

View raw message