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 2016/01/19 15:38:39 UTC

[jira] [Created] (OAK-3895) Expose jmx to invalidate cache entries

Vikas Saurabh created OAK-3895:
----------------------------------

             Summary: 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)