[SERVER-78615] Poor view drop performance leads to replication lag Created: 03/Jul/23  Updated: 26/Jan/24  Resolved: 13/Dec/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 6.0.6
Fix Version/s: 7.3.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: David Dominguez Sal
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Problem/Incident
Related
related to SERVER-83496 Better handling of the tests that set... Backlog
related to SERVER-53870 Improve view creation performance ove... Closed
Assigned Teams:
Storage Execution EMEA
Backwards Compatibility: Fully Compatible
Sprint: 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
Participants:
Linked BF Score: 10

 Description   

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.



 Comments   
Comment by Githook User [ 13/Dec/23 ]

Author:

{'name': 'David Dominguez-Sal', 'email': 'david.dominguez@mongodb.com', 'username': 'david-dominguez-sal'}

Message: SERVER-78615: Update fallback_observer to update the dropped view from the catalog, instead of reconstructing all views

GitOrigin-RevId: eb12c11bc4c2584f010e7bceebd8f9d502777c09
Branch: master
https://github.com/mongodb/mongo/commit/8ba916778b6789c16e6e693eea123daef7f2e601

Generated at Thu Feb 08 06:38:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.