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

CollMod should take distlock on timeseries bucket ns

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Sharding EMEA
    • ALL

      and stop migration on it as well.

      When running collMod against a timeseries collection, we use the original ns (view ns) when creating the coordinator doc (and this gets used by the ddl coordiantor to take dist locks). It also uses the original ns when stopping migrations here

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: