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 2015/04/21 13:42:59 UTC

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

    [ https://issues.apache.org/jira/browse/OAK-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504820#comment-14504820 ] 

Vikas Saurabh commented on OAK-2792:
------------------------------------

[~mreutegg], can you please review if such an approach makes sense?

(cc [~chetanm])

> Investigate feasibility/advantages of log-taling mongo op-log to invalidate cache
> ---------------------------------------------------------------------------------
>
>                 Key: OAK-2792
>                 URL: https://issues.apache.org/jira/browse/OAK-2792
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: mongomk
>            Reporter: Vikas Saurabh
>            Priority: Critical
>
> 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)