You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/08/20 22:53:00 UTC
[jira] [Commented] (GEODE-7089) Possible memory leak due to failure
to clean up client's registration queue
[ https://issues.apache.org/jira/browse/GEODE-7089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911790#comment-16911790 ]
ASF subversion and git services commented on GEODE-7089:
--------------------------------------------------------
Commit 5d0153ad4adb1612a1083673f98b1982819a6589 in geode's branch refs/heads/develop from Ryan McMahon
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5d0153a ]
GEODE-7089: Each client registration thread uses its own queue
Co-authored-by: Ryan McMahon <rm...@pivotal.io>
Co-authored-by: Donal Evans <do...@pivotal.io>
> Possible memory leak due to failure to clean up client's registration queue
> ---------------------------------------------------------------------------
>
> Key: GEODE-7089
> URL: https://issues.apache.org/jira/browse/GEODE-7089
> Project: Geode
> Issue Type: Bug
> Components: client queues
> Reporter: Ryan McMahon
> Assignee: Ryan McMahon
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> It is possible for a client's queue to leak and never be removed from the ClientRegistrationEventQueueManager's collection, which will result in it collecting events indefinitely and ultimately cause an OOM exception. This can happen if the registration fails for any reason (GII failed due to a peer crashing, unforseen serialization issues while copying the queue, etc). If the client does not retry on the same server after failure, the queue will leak. This is because we currently only remove the queue once a successful registration is performed, but its possible the client will just go to a different server on its next attempt.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)