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

Use read concern majority when connected to a replica set

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5.16, 1.6.0
    • Component/s: mongomk
    • Labels:

      Description

      Mongo 3.2 introduces new query option: readConcern. It allows to read only these changes that have been already committed to the majority of secondary instances.

      It prevents stale reads - a situation in which a change has been committed on the primary (and read from it), but due to the network partition a new primary is elected and the change is rolled back.

      We should use this new option (together with w:majority implemented in OAK-3554) when running Oak on MongoDB replica set.

      References:

        Attachments

        1. OAK-4069-3.patch
          29 kB
          Tomek Rękawek
        2. OAK-4069-2.patch
          30 kB
          Tomek Rękawek
        3. OAK-4069.patch
          25 kB
          Tomek Rękawek

          Issue Links

            Activity

              People

              • Assignee:
                tomek.rekawek Tomek Rękawek
                Reporter:
                tomek.rekawek Tomek Rękawek
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: