[
https://issues.apache.org/jira/browse/OAK-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777932#comment-16777932
]
Michael Dürig commented on OAK-8071:
------------------------------------
[~ahanikel], could you have a look at this one:
[https://github.com/mduerig/jackrabbit-oak/commits/OAK-8071-logging]
this should be simple enough and low risk to backport.
There is an issue though with the way we detect the current commit crossing the
gc boundary (with this branch as well as with the JMX variant): at the point in
time where {{Commit#gcGeneration}} is set to a non {{null}} value, the
potentially time consuming rewriting has already taken place. However, it is
this rewriting that we want to detect in the first place. Currently the only
simple enough approach I'm seeing is to generally rely on the time it takes for
a commit to complete.
> 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)
