[SERVER-58196] Investigate possibly adding a level of indirection when recording shard names to disk to reduce work when a shardName changes Created: 01/Jul/21  Updated: 06/Dec/22  Resolved: 29/Jul/21

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

Type: Improvement Priority: Major - P3
Reporter: Lamont Nelson Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Participants:

 Description   

When we persist shard names to disk in config metadata, and the shard changes it's name, the persisted records will now point to unknown shards. One idea that came out of the help ticket post-mortem was to introduce a level of indirection such that persisted records will "point to" a logical record for the shard (similar to a foreign key in a relational system). This ticket is to investigate if this would be helpful for existing code and future code; and also determine the level of effort if it is.


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