[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: |
|
||||||||||||
| 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 (
This ticket would extend the accumulators to be used for performance improvements on top of its existing purpose of functionally breaking dependencies. |