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

Remove unnecessary clearDbInfo in DDLs and rely on the implicit clear of the release of the critical section

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.2.0-rc0
    • Affects Version/s: 8.1.0-rc0, 8.0.0
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • v8.1, v8.0
    • CAR Team 2025-03-17
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      During database metadata DDL operations, we explicitly clear the database metadata from the DSS on the primary node and by writing a special flag in the config.cache.databases collection on secondary nodes.

      While this approach works, we should start relying on the implicit clearing that occurs when the critical section is released for secondary nodes and on ShardingRecoveryService::FilteringMetadataClearer() for primary nodes.

            Assignee:
            pol.pinol@mongodb.com Pol Pinol
            Reporter:
            pol.pinol@mongodb.com Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None