Hi Assaf, There is some information about tuning the JVM’s garbage collection parameters to work with eviction available here: http://geode.apache.org/docs/guide/managing/heap_use/heap_management.html#resource_manager <http://geode.apache.org/docs/guide/managing/heap_use/heap_management.html#resource_manager>
Best, Jared > On Dec 13, 2016, at 11:26 AM, <[email protected]> > <[email protected]> wrote: > > Hi Eric, > > Thanks for the quick response! > Shutting down the server is problematic for me. In a real scenario I won’t > remove all items but only some of them, thus the server still contains data > but have free space – still I will get the exception. Shutting down the > server will cause me to lose other entries – I’m afraid it’s not applicable > to me. > > I also understand that I can’t really control GC collection, so how does the > critical-threshold is expected to work? Once you reach it you can’t add more > items to server even if you removed some. > > Thanks. > > From: Eric Shu [mailto:[email protected]] > Sent: יום ג 13 דצמבר 2016 21:21 > To: [email protected] > Subject: Re: Geode memory handling issues > > I am not sure if GC collection can be controlled. One possible way to work > around this is to shut down the server and restart it. > > Also you may want to try offheap region to cope this issue? > > Regards, > Eric > > On Tue, Dec 13, 2016 at 11:02 AM, <[email protected] > <mailto:[email protected]>> wrote: > Hi, > > I am facing some issues with geode memory/resource management. > I have simple environment with a single locator and a single server, both are > launched via gfsh. > The server is started with initial-heap=max-heap=4GBand with > critical-heap-percentage=70%. > I also created a single region of type partition using gfsh. > > In addition, I created a simple client application (client-server topology, > accessing the region via ClientCache PROXY). The client simply iteratively > put data elements (of 100MB each) into the region. Upon putting total size of > ~70% of 4GB, I get exception on client side which tells the server is working > at low memory as expected – so far so good. > While observing the server metrics (using show metrics) I see that the server > holds data entries as expected and the heap usage and total heap size are > fine too. > > Now, I’m removing all elements from the region – the server metrics after > this operation shows that the elements count is 0 (i.e. the server is empty) > but still heap usage is high (probably because GC didn’t collect freed > items). That’s shouldn’t bother me, but the problem is if I’m trying to put > additional elements into the region now I still get the exception on client. > Although the server is empty the client can’t put items into it and this is > very problematic from user point of view. > > I tried to play with GC flags, change GC to G1 but with no success. I can’t > control GC collection – having an idle empty server with no way to add > elements to it. > > What am I missing here? Is there some other configuration I should follow? > > Thanks. > > Assaf Waizman > SW Architect | Process Diagnostics and Control | Applied Materials > 9 Oppenheimer Street, Rehovot, 76705. Israel. > Office +972.8.948.8661 <tel:%2B972.8.948.8661> | Mobile +972.54.80.10.799 | > Fax +972.8.948.8848 <tel:%2B972.8.948.8848>
