[
https://issues.apache.org/jira/browse/OAK-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774913#comment-16774913
]
Michael Dürig commented on OAK-8071:
------------------------------------
[~dulceanu], in summary: performance is not an issue as with the [second
commit|https://github.com/mduerig/jackrabbit-oak/commit/0dd87632ae6ec2228ac35fcdc8e919982559fb16]
stack trace collection will not be eager any more. The performance regression
only shows up when looking at the [first
commit|https://github.com/mduerig/jackrabbit-oak/commit/fcc2c85182d16e4838645e3a35c43d358c687421]
in isolation.
Would be great if you could have another look and double check whether I missed
something.
> 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.10.1, 1.8.12
>
>
> Add logging / monitoring to detect the situation from OAK-8014.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
