You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2018/02/06 20:54:00 UTC

[jira] [Resolved] (OAK-5056) Improve GC scalability on TarMK

     [ https://issues.apache.org/jira/browse/OAK-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig resolved OAK-5056.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.10)
                       (was: 1.9.0)
                   1.8.0

> Improve GC scalability on TarMK
> -------------------------------
>
>                 Key: OAK-5056
>                 URL: https://issues.apache.org/jira/browse/OAK-5056
>             Project: Jackrabbit Oak
>          Issue Type: Epic
>          Components: segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>            Priority: Major
>              Labels: gc, scalability
>             Fix For: 1.8.0
>
>
> This issue is about making TarMK gc more scalable: 
> * how to deal with huge repositories.
> * how to deal with massive concurrent writes.
> * how can we improve monitoring to determine gc health. 
> ** Monitor deduplication caches (e.g. deduplication of checkpoints)
> Possible avenues to explore:
> * Can we partition gc? (e.g. along sub-trees, along volatile vs. static content)
> * Can we pause and resume gc? (e.g. to give precedence to concurrent writes) 
> * Can we make gc a real background process not contending with foreground operations? 
> This issue is a follow up to OAK-2849, which was about efficacy of gc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)