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-8033) Node states sometimes refer to more than a single generation of segments after a full compaction
Date Thu, 07 Feb 2019 16:11:00 GMT

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

Michael Dürig updated OAK-8033:
-------------------------------
    Labels: TarMK candidate_oak_1_10 candidate_oak_1_6 candidate_oak_1_8  (was: TarMK)

> 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, 1.10
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>            Priority: Major
>              Labels: TarMK, candidate_oak_1_10, candidate_oak_1_6, candidate_oak_1_8
>
> 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.3#76005)

Mime
View raw message