jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (Jira)" <j...@apache.org>
Subject [jira] [Assigned] (OAK-3895) Expose jmx to invalidate cache entries
Date Wed, 04 Sep 2019 15:02:00 GMT

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

Marcel Reutegger reassigned OAK-3895:
-------------------------------------

    Assignee: Marcel Reutegger  (was: Vikas Saurabh)

> 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: Marcel Reutegger
>            Priority: Minor
>         Attachments: expose-jmx-invalidate-cache-OAK3895.patch
>
>
> 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
(v8.3.2#803003)

Mime
View raw message