[SERVER-76369] Accumulate state among early OpObservers Created: 20/Apr/23  Updated: 29/Oct/23  Resolved: 24/Apr/23

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

Type: Improvement Priority: Major - P3
Reporter: Matt Kneiser Assignee: Matt Kneiser
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-76425 Remove unused prePostImageOpTime from... Closed
is depended on by SERVER-76268 Move all unrelated work out of OpObse... Closed
is depended on by SERVER-76271 Remove OpObserverShardingImpl Depende... Closed
Related
related to SERVER-77366 add OpAccumulator to OpObserver::abou... Closed
Backwards Compatibility: Minor Change
Sprint: Execution Team 2023-05-01
Participants:

 Description   

The biggest inhibitor to splitting out the dependency of OpObserverShardingImpl and the forthcoming FallbackOpObserver is the fact that all OpObservers are given the same state.

 

This ticket is to design and implement a mechanism to accumulate state like OpTimes primarily from OpObserverImpl to be used by later OpObservers.



 Comments   
Comment by Githook User [ 24/Apr/23 ]

Author:

{'name': 'Matt Kneiser', 'email': 'matt.kneiser@mongodb.com', 'username': 'themattman'}

Message: SERVER-76369 Accumulate state among early OpObservers
Branch: master
https://github.com/mongodb/mongo/commit/df2b4fa0a434e7f24969f4fa67575b411282a796

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