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 2014/11/04 09:51:34 UTC
[jira] [Commented] (OAK-2192) Concurrent commit during compaction
results in mixed segments
[ https://issues.apache.org/jira/browse/OAK-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195892#comment-14195892 ]
Michael Dürig commented on OAK-2192:
------------------------------------
bq. We're advancing into the realm of OAK-2045, I'm wondering if it makes sense to merge the 2 issues.
Let's keep them separate. I added a comment to OAK-2045 that most of the discussion is currently here. Once we converge towards a solution I think it makes sense to split the patch into relevant fixes for OAK-2140, OAK-2045 and for this issue.
> Concurrent commit during compaction results in mixed segments
> -------------------------------------------------------------
>
> Key: OAK-2192
> URL: https://issues.apache.org/jira/browse/OAK-2192
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Labels: compaction, gc
> Attachments: OAK-2192-2.patch, OAK-2192-poc-fix.patch, OAK-2192-possible-test.patch, OAK-2192-v2.patch, OAK-2192-v3.patch, OAK-2192.patch
>
>
> Changes that are committed during a segment store compaction run will be compacted on top of the already compacted changes. However the compactor uses the wrong before state in this case. Instead of compacting against the compacted before state it uses the un-compacted before state. The resulting state will thus contain references to un-compacted state, making those not eligible for later clean up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)