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

Investigate why reloadViews need in FallbackOpObserver::onDelete

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

      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 Unassigned
            Reporter:
            adam.farkas@mongodb.com Wolfee Farkas
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: