[SERVER-56447] Resharding temp chunks should use its own collection UUID Created: 28/Apr/21  Updated: 27/Oct/23  Resolved: 28/Apr/21

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding NYC
Operating System: ALL
Participants:

 Description   

It currently uses the UUID of the original collection when creating the temp chunks and temp coll:

https://github.com/mongodb/mongo/blob/b46ac14ee3895b8129069c8f1b03e3820ebcea99/src/mongo/db/s/resharding/resharding_coordinator_service.cpp#L568

https://github.com/mongodb/mongo/blob/b46ac14ee3895b8129069c8f1b03e3820ebcea99/src/mongo/db/s/resharding/resharding_coordinator_service.cpp#L713

https://github.com/mongodb/mongo/blob/b46ac14ee3895b8129069c8f1b03e3820ebcea99/src/mongo/db/s/resharding/resharding_coordinator_service.cpp#L755

This can potentially cause issues with the new catalog cache refresh pipeline:
https://github.com/mongodb/mongo/blob/2957e50d04bf5eb2d3ad2aabdd37f8a63b10835d/src/mongo/s/catalog/sharding_catalog_client_impl.cpp#L348



 Comments   
Comment by Randolph Tan [ 28/Apr/21 ]

My mistake. Original uuid is getSourceUUID, and is different from reshardingUUID

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