jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4585) Text extraction: runtime status monitoring
Date Thu, 04 Aug 2016 08:14:20 GMT

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

Thomas Mueller commented on OAK-4585:

I will backport this to 1.4 as well.

> Text extraction: runtime status monitoring
> ------------------------------------------
>                 Key: OAK-4585
>                 URL: https://issues.apache.org/jira/browse/OAK-4585
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>             Fix For: 1.4.6, 1.5.7
> Text extraction is sometimes slow, and, in case of a bug in the text extraction library,
can even get stuck in an endless loop.
> Right now, it is not easy to understand what is going on, even when looking at full thread
dumps. (Debug) log information about the current state of text extraction would be nice as
> I suggest we add debug level logging for the current extracted binary (content identity).
For larger binaries, we can also temporarily set the thread name (append "Extracting <contentIdentity>").
That way, it is relatively easy to see if text extraction is stuck simply looking at full
thread dumps, without having to change the log level and then reindex.

This message was sent by Atlassian JIRA

View raw message