You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2015/10/14 15:33:05 UTC

[jira] [Commented] (OAK-3516) Lucene index diagnostics

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

Davide Giannella commented on OAK-3516:
---------------------------------------

Didn't look into the code. Can't it be achieved by log4j appenders and logging levels?

> Lucene index diagnostics
> ------------------------
>
>                 Key: OAK-3516
>                 URL: https://issues.apache.org/jira/browse/OAK-3516
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: lucene
>            Reporter: Thomas Mueller
>
> To debug and optimize the Lucene copy-on-read and copy-on-write mechanisms, we should have a special mode where additional data is logged and / or additional operations are performed:
> - log all write operations (file name, position, length, content hash)
> - log all read operations
> - log all cache read/write operations
> - a mode where every local read internally also reads the remote binary and compares the data



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)