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-3705) Change default of compaction.forceAfterFail to false
Date Fri, 11 Dec 2015 11:19:10 GMT

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

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

> Change default of compaction.forceAfterFail to false
> ----------------------------------------------------
>
>                 Key: OAK-3705
>                 URL: https://issues.apache.org/jira/browse/OAK-3705
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: segmentmk
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: candidate_oak_1_0, candidate_oak_1_2, compaction, gc
>             Fix For: 1.3.12
>
>
> Having {{compaction.forceAfterFail}} set to {{true}} will block repository writes for
an extended period of time (minutes, probably hours) if all previous compaction cycles couldn't
catch up with the latest changes. I think this is not acceptable and we should change the
default to {{false}}: if compaction is not able to catch up the recommendation should be to
move it to a quieter time. 



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

Mime
View raw message