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] [Commented] (OAK-8071) Logging to detect commits carrying over from previous GC generation can block other threads from committing
Date Thu, 21 Feb 2019 20:44:00 GMT

    [ https://issues.apache.org/jira/browse/OAK-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774494#comment-16774494
] 

Michael Dürig commented on OAK-8071:
------------------------------------

At [https://github.com/mduerig/jackrabbit-oak/commit/0dd87632ae6ec2228ac35fcdc8e919982559fb16]
I added a timestamp to the monitoring of the queued commits. At the same time I refactored
the handling of processing the stack traces a bit deferring their evaluation to the point
where they are requested.

[~dulceanu], could you have a look?

> 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)

Mime
View raw message