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 "Michael Marth (JIRA)" <ji...@apache.org> on 2015/04/21 15:28:58 UTC

[jira] [Updated] (OAK-2792) Investigate feasibility/advantages of log-tailing mongo op-log to invalidate cache

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

Michael Marth updated OAK-2792:
-------------------------------
    Summary: Investigate feasibility/advantages of log-tailing mongo op-log to invalidate cache  (was: Investigate feasibility/advantages of log-taling mongo op-log to invalidate cache)

> Investigate feasibility/advantages of log-tailing mongo op-log to invalidate cache
> ----------------------------------------------------------------------------------
>
>                 Key: OAK-2792
>                 URL: https://issues.apache.org/jira/browse/OAK-2792
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>            Reporter: Vikas Saurabh
>
> It is observed that current cache invalidation logic has some issues (OAK-2187) and there is an Oak issue (OAK-2646) to investigate alternative cache invalidation logic. One such option is to log-tail mongo op-log (specific to mongo back-end obviously :)).
> This task is for investigating that approach.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)