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/06/16 13:26:05 UTC

[jira] [Resolved] (OAK-3797) SegmentTracker#collectBlobReferences should retain fewer SegmentId instances

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

Alex Parvulescu resolved OAK-3797.
----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.6)
                   1.5.4

fixed with http://svn.apache.org/viewvc?rev=1748722&view=rev

> SegmentTracker#collectBlobReferences should retain fewer SegmentId instances
> ----------------------------------------------------------------------------
>
>                 Key: OAK-3797
>                 URL: https://issues.apache.org/jira/browse/OAK-3797
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segmentmk
>            Reporter: Michael Dürig
>            Assignee: Alex Parvulescu
>              Labels: datastore, gc
>             Fix For: 1.5.4
>
>         Attachments: OAK-3797-segmentmk-v2.patch
>
>
> {{SegmentTracker#collectBlobReferences}} currently keeps a queue of yet unprocessed {{SegmentId}} instances internally. This potentially impacts the system as those instances are also tracked in the segment tracker's segment id tables. I think we should improve the implementation to not retain so many {{SegmentId}} instances and rely on arrays of {{msb}}, {{lsb}} instead. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)