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

Dropping a sharded timeseries collection could lead to inconsistent sharding catalog state

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 5.3.0-rc4, 5.0.9, 6.0.0-rc7
    • Component/s: None
    • Sharding EMEA
    • ALL
    • Hide

      Apply the following patch on top of r5.0.9-14-g51168428972
      reproducible_SERVER-66756.patch

      and run jstests/sharding/timeseries_drop.js in the sharding suites to reproduce the problem.

      Show
      Apply the following patch on top of r5.0.9-14-g51168428972 reproducible_SERVER-66756.patch and run jstests/sharding/timeseries_drop.js in the sharding suites to reproduce the problem.
    • Sharding EMEA 2022-06-27

      The concurrent execution of a shardCollection and a dropCollection on a timeseries collection could lead to an inconsistent catalog state, where the bucket nss is still registered in the sharding catalog config.collections but the view namespace is not registered locally on the primary shard.

        1. reproducible_SERVER-66756.patch
          7 kB

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: