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-3737) Compactor should log revisions acting upon
Date Fri, 11 Dec 2015 11:17:11 GMT

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

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

> Compactor should log revisions acting upon
> ------------------------------------------
>
>                 Key: OAK-3737
>                 URL: https://issues.apache.org/jira/browse/OAK-3737
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: segmentmk
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>            Priority: Blocker
>              Labels: candidate_oak_1_0, candidate_oak_1_2, compaction, gc
>             Fix For: 1.3.12
>
>
> For post mortem analysis it would be helpful to have the revisions that where involved
in a compaction run. I.e. the revision that was compacted, the revisions of the cycles (if
any) and the revision that is ultimately applied?



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

Mime
View raw message