Loading...

XML

Word

Printable

JSON

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

Assigned Teams:

Catalog and Routing
Sprint:
CAR Team 2025-10-27, CAR Team 2025-11-10, CAR Team 2025-11-24
CAR Domain/s:

🟥 DDL

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

The correct behavior of V2 change stream readers relies on the content of config.placementHistory being consistently initialized by InitializePlacementHistoryCoordinator (~~SERVER-109002~~) and AddShardCoordinator (~~SERVER-111796~~).

Since legacy server versions can also perform initialization procedures following different semantics (see ~~SERVER-81137~~), the schema of the initialization metadata documents needs to be enriched to properly distinguish this case - and repeat the initialization if needed (SERVER-111901).

is depended on by

SERVER-111901 Add lazy initialization of config.placementHistory upon the first targeting request from V2 change stream readers

Backlog

is related to

SERVER-111901 Add lazy initialization of config.placementHistory upon the first targeting request from V2 change stream readers

Backlog

SERVER-81137 Add feature flag to reset placement history on FCV upgrade

Closed

SERVER-109002 InitializePlacementHistoryCoordinator must drain any operation on the global catalog before generating its materialized view

Closed

SERVER-111796 Ensure that the initialization metadata of config.placementHistory get created as part of the first addShard commit

Closed

Assignee:: Paolo Polato
Reporter:: Paolo Polato
Participants:: Paolo Polato
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jul 25 2025 03:24:37 PM UTC
Updated:: Nov 10 2025 09:43:20 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates