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 "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2015/04/21 13:46:58 UTC

[jira] [Commented] (OAK-2793) Time limit for HierarchicalInvalidator

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

Vikas Saurabh commented on OAK-2793:
------------------------------------

[~mreutegg], I'd prototype this and post a rough comparison of performance drop due to excessive cache invalidation if any. BTW, the setup I'd be using it with would have a fairly small doc cache and would have persistent cache enabled. Would that be fine?

> Time limit for HierarchicalInvalidator
> --------------------------------------
>
>                 Key: OAK-2793
>                 URL: https://issues.apache.org/jira/browse/OAK-2793
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>            Reporter: Marcel Reutegger
>             Fix For: 1.3.0
>
>
> This issue is related to OAK-2646. Every now and then I see reports of background reads with a cache invalidation that takes a rather long time. Sometimes minutes. It would be good to give the HierarchicalInvalidator an upper limit for the time it may take to perform the invalidation. When the time is up, the implementation should simply invalidate the remaining documents.



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