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/07/22 13:58:04 UTC

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

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

Marcel Reutegger resolved OAK-2793.
-----------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 1.3.4)

Resolving as WONTFIX. With OAK-3002 the HierarchicalInvalidator is only used as a fallback. Otherwise cache entries are invalidated more efficiently based on journal information. 

> 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
>            Assignee: Marcel Reutegger
>              Labels: resilience
>         Attachments: OAK-2793-Time-limit-for-HierarchicalInvalidator.patch
>
>
> 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)