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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2017/02/17 12:22:41 UTC

[jira] [Created] (OAK-5703) The replica set info gets invalid cluster id

Tomek Rękawek created OAK-5703:
----------------------------------

             Summary: The replica set info gets invalid cluster id
                 Key: OAK-5703
                 URL: https://issues.apache.org/jira/browse/OAK-5703
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: core, mongomk
    Affects Versions: 1.6.0
            Reporter: Tomek Rękawek


A part of the replica set info provider (namely, the LocalChanges), uses the instance cluster id to find out whether Oak is being run in cluster.

However, the way in which MongoDocumentStore provides this clusterId to the LocalChanges class is not correct. It's taken from the DocumentMK.Builder, which works only for the case when it's being set explicitly in the configuration and doesn't work if Oak gets its clusterId automatically.

As a result, if the clusterId isn't set in the configuration, the LocalChanges class remains disabled and doesn't allow to use the secondary Mongo instances for find() and query() requests.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)