[SERVER-70174] Migration or contraction of a tenant’s collections Created: 03/Oct/22  Updated: 05/Dec/22

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Rishab Joshi (Inactive) Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Participants:

 Description   

Some no-op entries that are important for tracking change streams across a sharded cluster would probably not be written with a tenant ID (e.g. migrateChunkToNewShard). This means that in a Serverless sharded cluster, we wouldn’t be able to track the migration or contraction of a tenant’s collections across the shards on which their slices reside. This ticket is about revisiting this case and making any fixes if required.


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