Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-5703

The replica set info gets invalid cluster id

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.6.0
    • 1.7.0, 1.6.1, 1.8.0
    • core, mongomk
    • None

    Description

      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.

      Attachments

        1. OAK-5703.patch
          11 kB
          Tomek Rękawek

        Activity

          People

            Unassigned Unassigned
            tomek.rekawek Tomek Rękawek
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: