You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2016/12/05 10:59:58 UTC
[jira] [Commented] (OAK-5223) SegmentNodeStoreService components
don't unregister with the blobstore
[ https://issues.apache.org/jira/browse/OAK-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15721963#comment-15721963 ]
Alex Parvulescu commented on OAK-5223:
--------------------------------------
Had a chat with [~frm] and we cam to the conclusion that this comes from the fact that the reference to the {{blobStore}} is dynamic, when it doesn't really need to be [0], so one very good option is to make it a static reference, to force the entire service to shutdown and activate properly.
[0] https://github.com/apache/jackrabbit-oak/blob/trunk/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/SegmentNodeStoreService.java#L281
> SegmentNodeStoreService components don't unregister with the blobstore
> ----------------------------------------------------------------------
>
> Key: OAK-5223
> URL: https://issues.apache.org/jira/browse/OAK-5223
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Fix For: 1.6, 1.5.15
>
>
> There are a few components in the SegmentNodeStoreService ({{store}}, {{segmentNodeStore}}, {{gcMonitor}} and {{observerTracker}}) that aren't unregistered when the blobStore unregisters. So in the case of a blobStore unregister/register situation, they will be recreated but the old ones will not be closed properly.
> [edit] added all components that have a leak problem when the blob store binds/unbinds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)