Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-31032

Secondaries should default to 'available' read concern level when one is not specified

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2017-10-02
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the 'shardVersion' of a request is only ignored when 'available' read concern is set in that request. So the default is 'local' read concern when none is specified. This is desirable on primaries, but we wish to maintain v3.4 behavior on secondaries by defaulting to 'available' when none is specified.

      Update: the exception to a secondary request's default to 'available' read concern level is when afterClusterTime is specified without a level, in which case the default should be 'local'. As per SPEC-929.

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: