Primary node can retrieve routing table inconsistent with the data it owns during network partition

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When readConcern local is set, it is possible for a node that believes it is primary in a split brain scenario to retrieve a version of the routing table that it does not actually own. This can lead to the node returning orphaned documents, which is a violation of the local read concern.

              Assignee:
              [DO NOT USE] Backlog - Sharding Team
              Reporter:
              Gregory McKeon (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: