[SERVER-75307] Use the routing table to construct the historical placement doc on reshardCollection commit Created: 27/Mar/23  Updated: 29/Oct/23  Resolved: 01/Apr/23

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

Type: Bug Priority: Major - P3
Reporter: Paolo Polato Assignee: Paolo Polato
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-71613 Create a new JS test hook to validate... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-04-03
Participants:

 Description   

The commit of reshardCollection includes a statement to persist the updated placement metadata into config.placementHistory using the value of the recipientShards field of the DDL coordinator document.

Nevertheless, such value may not correspond to the true placement of the resharded collection, since it always includes the primary shard of the parent database (which may not own any chunk at the end of the operation) and the routing table should be accesses instead.



 Comments   
Comment by Githook User [ 31/Mar/23 ]

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-75307 Use the routing table to construct the historical placement doc on reshardCollection commit
Branch: master
https://github.com/mongodb/mongo/commit/7c2bb70cd9229988e54fbc53e9f1386e82a7eea0

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