[
https://issues.apache.org/jira/browse/OAK-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106805#comment-15106805
]
Vikas Saurabh commented on OAK-3895:
------------------------------------
Attaching documentmk label for now. I'm not sure if there are some cache around
segment too? Also, I was thinking for wiring this up the same way we get
consolidated cache stats - so, one impl would call up all registered
implementations (the only other one I know of is
{{MongoDocumentStore#nodesCache}}).
[~mreutegg], [~chetanm], thoughts?
> Expose jmx to invalidate cache entries
> --------------------------------------
>
> Key: OAK-3895
> URL: https://issues.apache.org/jira/browse/OAK-3895
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
>
> We have had some issues (e.g. OAK-3634) which put incorrect entry in the some
> cache. Currently, the only way to clean cache is to restart the instance (and
> remove persistent cache files if configured).
> So, it might be useful to expose some jmx to invalidate cache without
> restarting the instance. As a first step, I think we can clean all caches
> (which is equivalent to current setup but without restart). We can later
> expose invalidation methods for specific cases (say, {{cacheType, path, rev}}
> as applicable).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
