Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- auto-reverted

Assigned Teams:

Replication
Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2025-07-21, Repl 2025-08-04, Repl 2025-08-18
Linked BF Score:
200
Confidence Status:
None
Work Order:
3
Size Category:
TBD
CAR Domain/s:
None

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

The new OplogVisibilityManager needs to be created & owned somewhere with process lifetime, similar to other services that run on the ServiceContext. A pointer to this manager can be placed on the OperationContext as a decorable, or as a service and a decorable on the parent ServiceContext.

Once ~~SERVER-106673~~ is merged, we can create the pointers/references but defer instantiation until the feature flag is checked - we only want to enable the new behavior when instructed to by the feature flag.

This ticket is successful once ops have access to OplogVisibilityManager* for use when the feature flag is enabled.

is depended on by

SERVER-108849 Investigate whether timestamps can move backwards on rollback

Open

SERVER-106813 OplogVisibilityManager - track visibility when feature flag enabled

In Progress

is duplicated by

SERVER-107113 Initialize OplogVisibilityManager globally with pointer to Oplog Collection

Closed

is related to

SERVER-106673 Update oplog visibility project code to compile with bazel

Closed

Assignee:: Kyra Ramesh Krishna (Inactive)
Reporter:: Myles Hathcock
Participants:: Githook User, Kyra Ramesh Krishna, Mothra Jira Bot, Myles Hathcock
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Jun 26 2025 08:50:25 PM UTC
Updated:: Aug 12 2025 02:20:51 PM UTC
Confidence Status Last Update:: 28/Jul/25 3:52 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates