-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 6.0.6
-
Component/s: None
-
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
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.
- depends on
-
SERVER-89285 Reload views when onInitialDataAvailable happens
- Blocked
-
SERVER-90268 Investigate potential issues due to lack of ordering in onInitialDataAvailable calls
- Open
- related to
-
SERVER-90332 Revert SERVER-78615
- Closed
-
SERVER-83496 Better handling of the tests that set the system.views collection to inconsistent contents
- Backlog
-
SERVER-90682 Keep the in-memory status of views up-to-date without reloading them on every operation in FallbackOpObserver
- Backlog
-
SERVER-53870 Improve view creation performance over time
- Closed