Store placement changes into config.placementHistory when a moveChunk/Range() command gets committed on the config server

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The completion of a chunk migration may a change to the placement metadata of the collection it belongs to:

      • the donor gives away the last chunk of nss it was owning
      • the recipient takes ownership of its first chunk of nss

      Such events must be matched with related writes to config.placementHistory.

            Assignee:
            Paolo Polato
            Reporter:
            Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: