[OAK-2793] Time limit for HierarchicalInvalidator

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: core, mongomk
• Labels: resilience
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 21/Apr/15 11:42
• Updated: 22/Jul/15 11:57
• Resolved: 22/Jul/15 11:57

Description

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.

Issue Links

• relates to: OAK-3002 Optimize docCache and docChildrenCache invalidation by filtering using journal
• relates to: OAK-2646 Look for alternative cache invalidation logic for better performance