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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/03/04 12:59:04 UTC

[jira] [Updated] (OAK-2572) Include cache invalidation stats in logs related to background operations

     [ https://issues.apache.org/jira/browse/OAK-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra updated OAK-2572:
---------------------------------
    Attachment: OAK-2572.patch

[patch|^OAK-2572.patch] for the same. It introduces a new {{CacheInvalidationStats}} interface to wrap invalidation result and make {{DocumentStore#invalidateCache}} return that. For now only {{MongoDocumentStore}} return the stats and other return null

[~mreutegg] [~reschke] Can you have a look

> Include cache invalidation stats in logs related to background operations
> -------------------------------------------------------------------------
>
>                 Key: OAK-2572
>                 URL: https://issues.apache.org/jira/browse/OAK-2572
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.2, 1.0.13
>
>         Attachments: OAK-2572.patch
>
>
> Currently {{DocumentNodeStore}} logs at info level some stats when the background operation takes more than 10 sec. In many cases it is seen that time is spent in read but we do not get any insight around where it is spent. 
> As one of the major work of backgroundRead is to invalidate cache it would be good to include the cache stats



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