You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anilkumar Gingade (Jira)" <ji...@apache.org> on 2020/08/10 18:37:00 UTC

[jira] [Updated] (GEODE-5772) fix the potential cache leak caused by reconnect

     [ https://issues.apache.org/jira/browse/GEODE-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anilkumar Gingade updated GEODE-5772:
-------------------------------------
    Labels: GeodeOperationAPI pull-request-available  (was: pull-request-available)

> fix the potential cache leak caused by reconnect
> ------------------------------------------------
>
>                 Key: GEODE-5772
>                 URL: https://issues.apache.org/jira/browse/GEODE-5772
>             Project: Geode
>          Issue Type: Bug
>          Components: core
>            Reporter: Xiaojian Zhou
>            Priority: Major
>              Labels: GeodeOperationAPI, pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Customer reported when reconnect happens, the memory usage will increase a lot. 
>  
> After investigation with Barry and Anil, we found there're one or more cache instances are still alive after reconnect closed it and created a new live cache. 
>  
> We walk through the code and fix some potential places that still hold the cache reference. 
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)