[SERVER-30542] Primary node can retrieve routing table inconsistent with the data it owns during network partition Created: 07/Aug/17  Updated: 27/Oct/23  Resolved: 30/Sep/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Gregory McKeon (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Gone away Votes: 0
Labels: sharding-DDL-bugs
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

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.



 Comments   
Comment by Kaloian Manassiev [ 30/Sep/20 ]

As of the changes done for SERVER-47982, this is no longer the case.

Generated at Thu Feb 08 04:24:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.