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] [Commented] (OAK-2192) Concurrent commit during compaction results in mixed segments
Date Mon, 15 Dec 2014 12:58:13 GMT

    [ https://issues.apache.org/jira/browse/OAK-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246621#comment-14246621
] 

Michael Dürig commented on OAK-2192:
------------------------------------

Committed the v10 patch at http://svn.apache.org/r1645637 including a fixes from Alex for
the deadlock problem and the wrong constant values in {{SegmentNodeStoreService}}. 

bq. The proper wrapping of the callback into the semaphore lock will not work then, right?
One way to enforce the setup of the callbacks is to make the respective method in {{CompactionStrategy}}
abstract. Will follow up on this. 

> 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, segmentmk
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: compaction, gc
>             Fix For: 1.0.9
>
>         Attachments: OAK-2192-2.patch, OAK-2192-poc-fix.patch, OAK-2192-possible-test.patch,
OAK-2192-v10-branch-1.0.patch, OAK-2192-v10.patch, OAK-2192-v2.patch, OAK-2192-v3.patch, OAK-2192-v4.patch,
OAK-2192-v5.patch, OAK-2192-v6.patch, OAK-2192-v7.patch, OAK-2192-v8-branch-1.0.patch, OAK-2192-v8.patch,
OAK-2192-v9-branch-1.0.patch, OAK-2192-v9.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)

Mime
View raw message