[SERVER-60805] Get rid of the ShardId field of the recipient coordinator document Created: 19/Oct/21  Updated: 29/Oct/23  Resolved: 08/Nov/21

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

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Sergi Mateo Bellido
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-11-01, Sharding EMEA 2021-11-15
Participants:

 Description   

Note that this ticket is to discuss about the shard-id field that was introduced on the recipient coordinator document as part of SERVER-60645.

This field is there just for debugging purposes + being able to reuse some utils such as the ActiveMigrationRegistry. The underlying problem with the shard ids is that they are not  portable when we do an snapshot of a sharded cluster and restore it in another cluster. In this situation we have to run some scripts to properly update the metadata.



 Comments   
Comment by Githook User [ 05/Nov/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-60805 Rename the ShardId field on the recipient doc
Branch: master
https://github.com/mongodb/mongo/commit/9ad49bff85da84d36f2438ec3d8bae0a8af0e19e

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