[jira] [Comment Edited] (OAK-2408) Investigate ways to make revision gc more precise

["Michael Dürig (JIRA)" <ji...@apache.org>]

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

Michael Dürig edited comment on OAK-2408 at 2/6/15 5:28 PM:
------------------------------------------------------------

Just {{git push -f}}'ed my latest stuff on https://github.com/mduerig/jackrabbit-oak/commits/OAK-2408-2
* Writing proxy segments now
* First effort to interpret the proxy segment by adding {{Segment.Reader}}, which would take care of the offset re-mapping. 

Currently all tests in {{org.apache.jackrabbit.oak.plugins.segment}} pass except for {{CheckpointTest#testRelease}}. Also all tests in {{RepositoryTest}} fail. I find this a bit scary as it indicates that our (unit) test coverage of the SegmentMK is to low. We probably need to invest quite a bit of time there before we introduce any bigger refactorings into trunk. 


was (Author: mduerig):
Just {{git push -f}}'ed my latest stuff on https://github.com/mduerig/jackrabbit-oak/commits/OAK-2408-2:
* Writing proxy segments now
* First effort to interpret the proxy segment by adding {{Segment.Reader}}, which would take care of the offset re-mapping. 

Currently all tests in {{org.apache.jackrabbit.oak.plugins.segment}} pass except for {{CheckpointTest#testRelease}}. Also all tests in {{RepositoryTest}} fail. I find this a bit scary as it indicates that our (unit) test coverage of the SegmentMK is to low. We probably need to invest quite a bit of time there before we introduce any bigger refactorings into trunk. 

> 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
>             Fix For: 1.2, 1.0.12
>
>
> 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)