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

Fix enableSharding call in sbe_plan_cache_does_not_block_range_deletion.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Sharding EMEA 2023-10-30
    • 144

      In sbe_plan_cache_does_not_block_range_deletion.js, the call to enableSharding uses `primaryShard: st.shard0.shardname` to set the primary shard to the correct shard. However, the variable name is st.shard0.shardName and so this ends up sending `primaryShard: undefined`, which randomly assigns the dbprimary to a shard.

       

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: