jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Updated] (OAK-3501) PersistedCompactionMap could release reference to records early
Date Fri, 11 Dec 2015 11:24:11 GMT

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

Michael Dürig updated OAK-3501:
-------------------------------
    Labels: candidate_oak_1_0 candidate_oak_1_2 compaction gc  (was: compaction gc)

> PersistedCompactionMap could release reference to records early
> ---------------------------------------------------------------
>
>                 Key: OAK-3501
>                 URL: https://issues.apache.org/jira/browse/OAK-3501
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segmentmk
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>            Priority: Minor
>              Labels: candidate_oak_1_0, candidate_oak_1_2, compaction, gc
>             Fix For: 1.3.8
>
>         Attachments: OAK-3501-v2.patch, OAK-3501.patch
>
>
> Whenever a PersistedCompactionMap becomes empty it will be eventually dropped from the
compaction maps chain. this will happen on the next compaction cycle, which happens post-cleanup.
so we're potentially keeping a reference to some collectable garbage for up to 2 cycles.
> I'd like to propose a patch that allows for eagerly nullifying the reference to the records,
making this interval shorter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message