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

New createCollection coordinator unconditionally create initial chunks with collection UUID

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: Backlog
    • Component/s: Sharding
    • Sharding EMEA
    • ALL
    • Hide

      Run jstests/sharding/basic_drop_coll.js with featureFlagShardingFullDDLSupport enabled and featureFlagShardingFullDDLSupportTimestampedVersion disabled

      Show
      Run jstests/sharding/basic_drop_coll.js with featureFlagShardingFullDDLSupport enabled and featureFlagShardingFullDDLSupportTimestampedVersion disabled

      If the shardingFullDDLSupportTimestampedVersion feature flags is enable the chunks in config.chunks are indexed by and contains the UUID of the collection. While the legacy createCollection code takes this into account, the new createCollection coordinator doesn't check for this feature flags and unconditionally attach the UUID fields to the initial chunks

      We didn't spot this bug till now because we either test with all the feature flags enable or with all of them disable.

            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: