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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2015/02/23 10:46:12 UTC
[jira] [Assigned] (OAK-2501) add more trace-logging to mongoMk to
debug performance issues
[ https://issues.apache.org/jira/browse/OAK-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger reassigned OAK-2501:
-------------------------------------
Assignee: Marcel Reutegger
> add more trace-logging to mongoMk to debug performance issues
> -------------------------------------------------------------
>
> Key: OAK-2501
> URL: https://issues.apache.org/jira/browse/OAK-2501
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.0.11
> Reporter: Stefan Egli
> Assignee: Marcel Reutegger
> Fix For: 1.0.12
>
> Attachments: oak.2501.patch, oak.2501.trunk.patch
>
>
> Debugging performance issues within mongoMk is currently somewhat more challenging that it would have to - IMO because there is no easy logger that can be turned on to get some performance numbers. Ie currently for figuring out what's going on in mongoMk you can set the log level to TRACE for the following loggers:
> {code}
> org.apache.jackrabbit.oak.plugins.observation.EventGenerator
> org.apache.jackrabbit.oak.plugins.document.mongo.MongoDocumentStore
> org.apache.jackrabbit.oak.plugins.document.NodeDocument
> org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore
> {code}
> while you might still not catch all interesting and crucial details.
> So the suggestion is to add a dedicated logger which is used at a couple of neuralgic locations (eg in observation event generation, cache handling, diffChildren, findUncached etc)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)