[OAK-3878] Avoid caching of NodeDocument while iterating in BlobReferenceIterator

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.7.11, 1.8.0
• Component/s: documentmk
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 14/Jan/16 07:06
• Updated: 13/Nov/17 13:55
• Resolved: 06/Nov/17 09:05

Description

BlobReferenceIterator in DocumentMK makes use of DocumentStore API to query the NodeDocument. This would cause all those NodeDocuments to be added to cache in DocumentStore. Due to this when blob gc is running cache usage would not be that effective due to all the associated churn.

As these NodeDocument are only required for BlobGC logic and its not expected that this document would read again soon it would be better to skip caching of these documents within DocumentStore

Similar requirement exist in VersionGC logic but there we use direct store based API which does not add such documents to the cache

Issue Links

• is related to: OAK-6806 RDBDocumentStore: version GC does not scale when there are many docs with long paths
• relates to: OAK-5855 RDBDocumentStore: improve query support for VersionGC