Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- repl-shortlist

Assigned Teams:

Replication
Sprint:
CAR Team 2025-03-31
Confidence Status:
None
Work Order:
3

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

~~SERVER-90360~~ introduced new interfaces to simplify the logic of components that keep some durable state and some in-memory state on synch.

The CAR team started to work on porting our components to these new interfaces (SERVER-91505), but we realized that onConsistentDataAvailable function, when it is being executed due to a rollback operation, it doesn't have any information about the namespaces that had some oplog entries rollbacked. This is a regression compared with the old interfaces, so we were just wondering if we could add this extra info to the new interface.

is depended on by

SERVER-91505 [Catalog] Adopt the improved repl interfaces to keep in-memory states in sync with data

Blocked

SERVER-91674 [Cluster Server Parameters] Adopt the improved repl interfaces to keep in-memory states in sync with data

Blocked

SERVER-91925 [ShardingInitializationMongoD] Adopt the improved repl interfaces to keep in-memory states in sync with data

Blocked

SERVER-91926 [ShardingRecoveryService] Adopt the improved repl interfaces to keep in-memory states in sync with data

Blocked

SERVER-91927 [UserWritesRecoverableCriticalSectionService] Adopt the improved repl interfaces to keep in-memory states in sync with data

Blocked

SERVER-91928 [VectorClockMongoD] Adopt the improved repl interfaces to keep in-memory states in sync with data

Blocked

SERVER-91929 [ConfigServerOpObserver] Adopt the improved repl interfaces to keep in-memory states in sync with data

Blocked

SERVER-91930 [ShardServerOpObserver] Adopt the improved repl interfaces to keep in-memory states in sync with data

Blocked

is related to

SERVER-103814 Recovering the DatabaseShardingState after a rollback should only be triggered by specific namespaces

Closed

(3 is depended on by, 1 is related to)

Assignee:: Unassigned
Reporter:: Sergi Mateo Bellido
Participants:: Sergi Mateo Bellido
Votes:: 0 Vote for this issue
Watchers:: 12 Start watching this issue

Created:: Mar 19 2025 10:14:00 AM UTC
Updated:: May 14 2025 11:57:25 AM UTC
Confidence Status Last Update:: 20/Mar/25 4:49 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates