jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1643) Implement BlobReferenceIterator optimized for Mongo
Date Sat, 29 Mar 2014 19:35:17 GMT

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

Chetan Mehrotra commented on OAK-1643:

Added a MogoBlobReferenceIterator in http://svn.apache.org/r1583055

[~tmueller] and [~amitj_76] Can you review the impl done. 

Also I am directing the query to secondary given that GC logic looks for binaries which have
not been modified/added in past 1 hr (default). Would that be safe assumption or should we
prefer primary?

> Implement BlobReferenceIterator optimized for Mongo
> ---------------------------------------------------
>                 Key: OAK-1643
>                 URL: https://issues.apache.org/jira/browse/OAK-1643
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 0.20
> Current BlobReferenceIterator works on DocumentStore API due to which it is not able
to make use of Mongo specific optimization and has few issues like
> * It floods the cache with NodeDocument fetched just for binary extraction (OAK-1568)
> * It implements its own pagination where it can rely on Mongo DBCursor (OAK-1567)
> * For Blob GC case it would be preferable if the query can be routed to Mongo replica
instead of loading primary
> Having an impl which works directly on DBCollection level would be better

This message was sent by Atlassian JIRA

View raw message