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 "Miroslav Smiljanic (Jira)" <ji...@apache.org> on 2020/06/04 14:18:00 UTC
[jira] [Comment Edited] (OAK-9099) Improve segment write resiliency
for remote segment store
[ https://issues.apache.org/jira/browse/OAK-9099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125946#comment-17125946 ]
Miroslav Smiljanic edited comment on OAK-9099 at 6/4/20, 2:17 PM:
------------------------------------------------------------------
Please find below proposal to deal with the issue (together with the test).
[^proposal.patch]
was (Author: smiroslav):
Please find below prosal to deal with the issue (together with the test).
[^proposal.patch]
> Improve segment write resiliency for remote segment store
> ----------------------------------------------------------
>
> Key: OAK-9099
> URL: https://issues.apache.org/jira/browse/OAK-9099
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-azure
> Affects Versions: 1.30.0
> Reporter: Miroslav Smiljanic
> Priority: Major
> Attachments: proposal.patch, test.patch
>
>
> SegmentWriteQueue is currently not handling runtime exception that potentialy can be thrown by remote segment store implementation. If that happens, segment reference will never be removed from *segmentsByUUID*, which can cause OAK-8986.
> Test case that demonstrates the problem:
> [^test.patch]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)