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

Get rid of the ShardId field of the recipient coordinator document

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.2.0
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding EMEA 2021-11-01, Sharding EMEA 2021-11-15

    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.

      Attachments

        Activity

          People

            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: