[
https://issues.apache.org/jira/browse/OAK-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080592#comment-14080592
]
Amit Jain commented on OAK-2007:
--------------------------------
Another option would be to not use the {{maxLastModifiedTime}} parameter (i.e.
set it to 0 when called from {{MarkSweepGarbageCollector}}). This should not
affect the garbage collection logic as {{MarkSweepGarbageCollector#sweep()}}
would take care of only deleting blobs whose modified time is less than
{{maxLastModifiedTime}}.
The advantage of the above approach would be that we don't need a new index on
lastMod or a compound index and more importantly the query will be covered by
the index and will be very fast and scalable as more blobs are added.
[~tmueller], [~chetanm] wydt?
> MongoBlobStore improvements
> ---------------------------
>
> Key: OAK-2007
> URL: https://issues.apache.org/jira/browse/OAK-2007
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob, mongomk
> Affects Versions: 1.0.2
> Reporter: Przemo Pakulski
> Attachments: OAK-2007.patch
>
>
> To collect all chunk identifiers (getAllChunkIds) hint is used to force "_id"
> index usage.
> This index doesn't help because query is using "lastMod" field. It also
> doesn't allow to leverage custom indexes if created. In result queries are
> pretty slow.
> Additionally consider to create index on "lastMod" field to speed-up all
> queries using this criteria.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
