[SERVER-61981] supporting_unique_index_check_is_versioned.js assumes that a refresh always reads from the primary node of the CSRS Created: 10/Dec/21  Updated: 06/Dec/22  Resolved: 16/Dec/21

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

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-60746 Client sessions are not causally cons... Open
Assigned Teams:
Sharding EMEA
Participants:

 Description   

The test wrongly assumes that the moveChunk command issued by a completely fresh mongos always succeeds. This is not always true: this refresh at the beginning of the moveChunk command in the mongos might not see that the collection was already sharded and throw an exception: the reason is that the CatalogCache reads from the config server with Nearest read preference so it might end up reading the majority committed information from a secondary node of the CSRS that hasn't replicated the shardCollection operation yet.


Generated at Thu Feb 08 05:53:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.