Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Minor Change
Sprint:
Execution Team 2023-05-01
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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.

depends on

SERVER-76425 Remove unused prePostImageOpTime from OpTimeBundle

Closed

is depended on by

SERVER-76268 Move all unrelated work out of OpObserverImpl into a miscellaneous FallbackOpObserver

Closed

SERVER-76271 Remove OpObserverShardingImpl Dependency on OpObserverImpl

Closed

related to

SERVER-77366 add OpAccumulator to OpObserver::aboutToDelete()

Closed

Assignee:: Matt Kneiser
Reporter:: Matt Kneiser
Participants:: Githook User, Matt Kneiser
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Apr 20 2023 09:10:53 PM UTC
Updated:: Oct 29 2023 09:22:43 PM UTC
Resolved:: Apr 24 2023 07:08:12 PM UTC
Confidence Status Last Update:: 20/Apr/23 10:00 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates