[ https://issues.apache.org/jira/browse/OAK-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509093#comment-14509093 ]
Vikas Saurabh edited comment on OAK-2793 at 4/23/15 1:57 PM: ------------------------------------------------------------- Attaching a [patch|^OAK-2793-Time-limit-for-HierarchicalInvalidator.patch] which would time out hierarchical cache invalidation. The patch reads a system property {{oak.mongo.cacheInvalidationTimeout}} (in ms). The default value is -1 which keeps timing out disabled. I don't have a setup to have a comparison of changes in invalidation time taken or drop in performance. I'd update the issue once I get around to benchmarking those numbers. was (Author: catholicon): Attaching a patch which would time out hierarchical cache invalidation. The patch reads a system property {{oak.mongo.cacheInvalidationTimeout}} (in ms). The default value is -1 which keeps timing out disabled. I don't have a setup to have a comparison of changes in invalidation time taken or drop in performance. I'd update the issue once I get around to benchmarking those numbers. > 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 > > 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)