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

Wait for range deletions before dropping collections when removing config server shard

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Sharding NYC 2023-04-17

    Description

      As of SERVER-75096, when the config server transitions to dedicated mode, it drops its drained sharded collections locally so it can later be added back without users directly dropping those collections on the config server first. The drop is in the first transitionToDedicatedConfigServer ran after all chunks and databases have been moved away. There may be pending range deletions though, so secondary reads may still be running or stale routers may target those collections with available read concern and expect to at least read orphans. For the same probabilistic guarantees as for normal migrations, we should only locally drop the collections after waiting for all pending range deletions to complete.

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: