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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2013/12/02 14:06:35 UTC

[jira] [Commented] (OAK-1246) Make AsynchIndexUpdate task to run only on a single node in a cluster

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

Alex Parvulescu commented on OAK-1246:
--------------------------------------

+1

> Make AsynchIndexUpdate task to run only on a single node in a cluster
> ---------------------------------------------------------------------
>
>                 Key: OAK-1246
>                 URL: https://issues.apache.org/jira/browse/OAK-1246
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.12
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>              Labels: cluster
>         Attachments: OAK-1246.diff
>
>
> Currently the {{AsynchIndexUpdate }} job which performs the indexing in background is run on every node in a cluster. This at times causes commit failures when running Oak in a cluster using Mongo MK. As merging of indexed content say Lucene is tricky to implement it would be better to restrict this job to run as a singleton in a cluster
> See http://markmail.org/thread/qff2fj7nqtbuhr4i for more discussion



--
This message was sent by Atlassian JIRA
(v6.1#6144)