Investigate why reloadViews need in FallbackOpObserver::onDelete

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In the function FallbackOpObserver::onDelete there is a CollectionCatalog::get(opCtx)->reloadViews(opCtx, nss.dbName()); call which seems to be unnecessary, but without it various exotic issues show up like here

      We have to find out why that happens.

              Assignee:
              Unassigned
              Reporter:
              Wolfee Farkas
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: