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

Make movePrimaryFailIfNeedToCloneMovableCollections only allow movePrimary to move unsharded collections that are not movable by moveCollection

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc13
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • v8.0
    • CAR Team 2024-06-24, CAR Team 2024-07-08

      This failpoint was introduced in SERVER-90465. Currently, it allows movePrimary to move all client system collections other than system.bucket collections. The reason is that based on how isAlwaysUntracked() is defined, in particular here, moveCollection doesn't support moving any system collections other than timeseries collections. The failpoint couldn't just call on isAlwaysUntracked() because it needs to allow movePrimary to move the ".system.resharding." collections created by the fuzzer since moveCollection doesn't have a way to tell that they not a real temporary timeseries collection so they are just by design rejected by moveCollection (this test case). This ticket is to investigate if we could add the system.resharding collections as a special case and call isAlwaysUntracked() instead of isLegalClientSystemNS(). So we are sure that we only allow collections that can never be tracked to be moved by movePrimary commands in the config transition suites. 

            Assignee:
            pol.pinol@mongodb.com Pol Pinol
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: