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

movePrimary set wrong collection version on new primary shard

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Critical - P2 Critical - P2
    • 7.1.0-rc0, 7.0.0-rc1, 6.0.7, 5.0.31
    • Affects Version/s: 4.2.24, 7.0.0-rc0, 6.0.5, 5.0.17, 4.4.21
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v7.0
    • Hide

      Originally tested version: r7.1.0-alpha-308-g9ec63c2a6fd

      Run the following test with:

      resmoke.py --suite=sharding jstests/sharding/repro_moveprimary_version_bug.js

      repro_moveprimary_version_bug.js

      Show
      Originally tested version: r7.1.0-alpha-308-g9ec63c2a6fd Run the following test with: resmoke.py --suite=sharding jstests/sharding/repro_moveprimary_version_bug.js repro_moveprimary_version_bug.js
    • Sharding EMEA 2023-05-01, Sharding EMEA 2023-05-15, CAR Team 2025-02-03
    • 150
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      MovePrimary creates collections on the new primary and set the shard version to UNSHARDED even if the collection is actually sharded.

        1. repro_moveprimary_version_bug.js
          1.0 kB

            Assignee:
            sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: