Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-58196

Investigate possibly adding a level of indirection when recording shard names to disk to reduce work when a shardName changes

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Sharding EMEA

    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.

      Attachments

        Activity

          People

            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            lamont.nelson@mongodb.com Lamont Nelson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: