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

Operations with {readConcern:available} do not treat the collection as UNSHARDED

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.8
    • Affects Version/s: 5.1.1, 5.2.1, 5.0.7
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Sharding EMEA 2022-04-18, Sharding EMEA 2022-05-02

      The available read concern is supposed to be used for situations where there are partitions or unavailable nodes in a sharded cluster which prevent it from properly enforcing the required causality guarantees.

      Because of this, we should be treating the collection as UNSHARDED.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: