[
https://issues.apache.org/jira/browse/OAK-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777917#comment-16777917
]
Axel Hanikel commented on OAK-8071:
-----------------------------------
[~mduerig] I agree with what you say about the gc generation. For the
CommitTracker, perhaps we can add a comment like
[https://github.com/ahanikel/jackrabbit-oak/commits/OAK-8071-2] to make clear
that the CommitTracker's dequeue and execute methods must now be used in
sequence within the same critical section?
> Logging to detect commits carrying over from previous GC generation can block
> other threads from committing
> -----------------------------------------------------------------------------------------------------------
>
> Key: OAK-8071
> URL: https://issues.apache.org/jira/browse/OAK-8071
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Priority: Blocker
> Fix For: 1.12, 1.11.0, 1.8.12, 1.10.2
>
>
> Add logging / monitoring to detect the situation from OAK-8014.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
