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

Do not wipe out renamed tags upon resuming the rename of sharded metadata

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.4, 5.1.0-rc0
    • Affects Version/s: 5.1.0, 5.0.2
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Sharding EMEA 2021-09-20
    • 133

      The updatesTag function is renaming the tags from the source to the target collection. This means that if a stepdown happens right after this call, the next time the operation will be resumed tags will be wiped out.

      The removeTagsMetadataFromConfig_notIdempotent call is not needed at all. Due to the original design of the rename operation, there is no need to delete the target collection tags since the rename will result in an early failure in case the target collection has tags.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: