[SERVER-78375] CollectionUUIDMismatch check occurs before shard version check Created: 23/Jun/23  Updated: 04/Jul/23  Resolved: 04/Jul/23

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

Type: Bug Priority: Major - P3
Reporter: Jordi Olivares Provencio Assignee: Jordi Olivares Provencio
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File shard_router_handle_staleconfig.js    
Issue Links:
Depends
depends on SERVER-77685 Server can return CollectionUUIDMisma... Closed
Duplicate
duplicates SERVER-77685 Server can return CollectionUUIDMisma... Closed
Assigned Teams:
Sharding EMEA
Operating System: ALL
Sprint: Execution EMEA Team 2023-07-10
Participants:

 Description   

In SERVER-77685 we discovered that the CollectionUUIDMismatch check is performed before checking the shard version. The order of those checks previously were inverted but SERVER-68337 mistakenly flipped them.

The first ticket fixes the issue in AutoGetCollection but for Shard Role acquisitions we copied the faulty logic.



 Comments   
Comment by Kaloian Manassiev [ 29/Jun/23 ]

jordi.olivares-provencio@mongodb.com since you are fixing SERVER-77685, I am assigning this to you to carry over the fix into the acquisitions API as well.

Comment by Jordi Olivares Provencio [ 23/Jun/23 ]

The attached test reproduces the failure: shard_router_handle_staleconfig.js

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