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

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

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

      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:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            greg.mckeon@mongodb.com Gregory McKeon (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: