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 "Julian Reschke (JIRA)" <ji...@apache.org> on 2019/07/12 13:50:00 UTC
[jira] [Updated] (OAK-8033) Node states sometimes refer to more
than a single generation of segments after a full compaction
[ https://issues.apache.org/jira/browse/OAK-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated OAK-8033:
--------------------------------
Labels: TarMK (was: TarMK candidate_oak_1_6)
> Node states sometimes refer to more than a single generation of segments after a full compaction
> ------------------------------------------------------------------------------------------------
>
> Key: OAK-8033
> URL: https://issues.apache.org/jira/browse/OAK-8033
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segment-tar
> Affects Versions: 1.10.0, 1.8.10, 1.6.16, 1.8.11
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Priority: Major
> Labels: TarMK
> Fix For: 1.12.0, 1.6.17, 1.10.1, 1.8.12
>
>
> Due to a regression introduced with OAK-7867 a full compaction can sometimes cause nodes that are written concurrently to reference segments from more than a single gc generation.
> This happens when the {{borrowWriter}} method needs to [create a new writer|https://github.com/apache/jackrabbit-oak/blob/trunk/oak-segment-tar/src/main/java/org/apache/jackrabbit/oak/segment/SegmentBufferWriterPool.java#L197-L201]. In this case the new writer will be of the generation of the current head state instead of the generation associated with the current write operation in progress.
>
> cc [~frm], [~ahanikel]
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)