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 "Davide Giannella (JIRA)" <ji...@apache.org> on 2019/01/09 17:05:11 UTC

[jira] [Updated] (OAK-7079) Enable oak-run indexing to connect to secondary node in Mongo replica set

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

Davide Giannella updated OAK-7079:
----------------------------------
    Fix Version/s: 1.12

> Enable oak-run indexing to connect to secondary node in Mongo replica set
> -------------------------------------------------------------------------
>
>                 Key: OAK-7079
>                 URL: https://issues.apache.org/jira/browse/OAK-7079
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk, run
>            Reporter: Chetan Mehrotra
>            Priority: Major
>             Fix For: 1.10.0, 1.12
>
>
> With OAK-6353 support for document order traversal based indexing has been added. Currently it connects to Mongo primary. 
> We need to test and validate if it can be made only to connect to Mongo secondary for below 2 cases
> # Pre created checkpoint - Here checkpoint is created already and then oak-run *only* connects to Mongo secondary
> # Online indexing - Here oak-run would also create checkpoint. However it would need to be ensured that when it performs the document order traversal query that query is handled by Mongo secondary and oak-run logic ensures that secondary node has the created checkpoint



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)