jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-4598) Collection of references retrieves less when large number of blobs added
Date Wed, 27 Jul 2016 11:46:20 GMT

    [ https://issues.apache.org/jira/browse/OAK-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395502#comment-15395502

Michael Dürig commented on OAK-4598:

Yes, this is the case. References to binaries would be shared across generations. 

To a certain case the same behaviour was already present before we introduced generational
gc, but on a finer scale: if - back then - a blob was referenced from an uncompacted segment
that was still referenced from memory then that reference would also have been reported twice.

> Collection of references retrieves less when large number of blobs added
> ------------------------------------------------------------------------
>                 Key: OAK-4598
>                 URL: https://issues.apache.org/jira/browse/OAK-4598
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segment-tar
>            Reporter: Amit Jain
>            Assignee: Francesco Mari
>              Labels: datastore, gc
>             Fix For: Segment Tar 0.0.8
> When large number of external blobs are added to the DataStore (50000) and a cycle of
compaction executed then the reference collection logic only returns lesser number of blob
references. It reports correct number of blob references when number of blobs added are less
indicatingsome sort of overflow.
> Another related issue observed when testing with lesser number of blobs is that the references
returned are double the amount expected, so maybe there should be some sort of de-duplication
which should be added.
> Without compaction the blob references are returned correctly atleast till 100000 (ExternalBlobId#testNullBlobId)

This message was sent by Atlassian JIRA

View raw message