Poor view drop performance leads to replication lag

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 6.0.6
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • Execution EMEA Team 2023-10-30, CAR Team 2023-11-13, CAR Team 2023-11-27, CAR Team 2023-12-11, CAR Team 2023-12-25
    • 200
    • None
    • 3
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      A replica secondary node will reload the whole view catalog every time there is a view deletion, under an exclusive lock on the database's views collection. It was previously decided to accept the poor performance because it was thought unreasonable that users would create/drop views so quickly and continuously. However, now we have a user case encountering poor performance.

              Assignee:
              Unassigned
              Reporter:
              Dianna Hohensee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: