[SERVER-68493] Investigate and document the existing infrastructure supporting the Change Stream functionality Created: 02/Aug/22  Updated: 09/Aug/22  Resolved: 09/Aug/22

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

Type: Task Priority: Major - P3
Reporter: Paolo Polato Assignee: Enrico Golfieri
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Sharding EMEA 2022-08-08, Sharding EMEA 2022-08-22
Participants:

 Description   

As part of the proposed design for PM-1939 we intend to generate System Change Stream events in correspondence with Sharding DDL operations that alter the subset of Shards containing at lest one chunk of the namespace targeted by a nss.watch() command.

Some of the desired change stream events (such as migrateChunkToNewShard and migrateLastChunkFromShard) are already being generated by the Server code to support C2C replication.

The objectives of this ticket are:

1. collect information on

  • where and how this events are being generated
  • where and how this events are being consumed
  • which is the logic supporting the propagation of the events

2. confirm that the existing code can be easily leveraged/extended to other DDL operations

3. update the "Following the execution" section of the Design document based on the outcome of the investigation


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