Failed to construct ShardingDDLCoordinators do not get released

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Hide

      Apply the provided patch and run:

      buildscripts/resmoke.py run --mongodSetParameters="{logComponentVerbosity: {sharding: 3}, featureFlagShardingFullDDLSupport: true, featureFlagShardingFullDDLSupportTimestampedVersion: true}" --suite=sharding jstests/sharding/ddl_coordinator_construction.js
      Show
      Apply the provided patch and run: buildscripts/resmoke.py run --mongodSetParameters="{logComponentVerbosity: {sharding: 3}, featureFlagShardingFullDDLSupport: true, featureFlagShardingFullDDLSupportTimestampedVersion: true}" --suite=sharding jstests/sharding/ddl_coordinator_construction.js
    • Sharding EMEA 2021-05-03
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      If a ShardingDDLCoordinator throws an exception during its construction phase, before to actually persist its state document on disk, it will reach the onCompletion task and will try to delete its state document, since this document doesn't exists the PrimaryOnlyServiceOpObserver::onDelete() won't be triggered and the instance won't be released from the POS.

        1. DDL_construction_failure_repro.patch
          3 kB

            Assignee:
            Tommaso Tocci
            Reporter:
            Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: