[
https://issues.apache.org/jira/browse/OAK-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved OAK-2408.
--------------------------------
Resolution: Done
Fix Version/s: (was: 1.3.3)
Any way to make revision gc more precise by introducing some kind of re-mapping
of pre compacted records to compacted records requires significant changes in
the design of the SegmentMK. Both of my prototypes resulted in touching nearly
every 2nd line of code without being nearly there.
The SegmentMK is designed to be fast and compact, which somewhat contradicts
maximal efficiency of revision gc. A redesign will most likely introduce shifts
in many area with unknown consequences across the rest of the stack.
My conclusion is that we need to fine tune revision gc *within* the current
design instead of coming up with a fundamental new approach. This is what
OAK-2849 is about. Resolving this task as done thus.
> Investigate ways to make revision gc more precise
> --------------------------------------------------
>
> Key: OAK-2408
> URL: https://issues.apache.org/jira/browse/OAK-2408
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: segmentmk
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Labels: gc
>
> Current approaches to revision garbage collection tend to be too conservative
> (too little space reclaimed, e.g. OAK-2045) or too aggressive (removing
> segments still being used, e.g. OAK-2384).
> This issue is to explore ways to make revision gc on TarMk more precise.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
