[SERVER-77373] Use OpStateAccumulator's to cache common state Created: 22/May/23  Updated: 26/Oct/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Matt Kneiser Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: former-storex-namer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-77057 Investigate slow down caused by OpObs... Closed
is related to SERVER-77364 Speed up OpObservers with a filter fr... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

OpObservers independently recompute and lookup global state. Like inRecoveryMode which requires several calls to ReplicationCoordinator. The onUpdate chain computes this state at least 4 times to filter events.

 

Currently the OpStateAccumulators are implemented post-7.0 (SERVER-76369) in a handful of methods (broadly speaking, the CRUD methods) that functionally require downstream OpObservers that observe the opTime allocated by OpObserverImpl.

 

This ticket would extend the accumulators to be used for performance improvements on top of its existing purpose of functionally breaking dependencies.


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