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

Allow migration errors due to concurrent shard key value updates in concurrency tests

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • Cluster Scalability 2024-09-02
    • 0

      We have a few concurrency tests that run migrations and updates that may update a doc's shard key. If a concurrent update changes a doc's shard key value for a doc in the range being migrated, the migration will fail. The tests already account for and ignore the errors thrown if the error happens during the main xfer mods phase, but not if it happens when waiting for commit (and still running xfer mods).

            Assignee:
            janna.golden@mongodb.com Janna Golden
            Reporter:
            janna.golden@mongodb.com Janna Golden
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: