[SERVER-64592] Make sure events with large documentKey do not crash change stream Created: 16/Mar/22  Updated: 06/Dec/22  Resolved: 17/Mar/22

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

Type: Task Priority: Major - P3
Reporter: Wenbin Zhu Assignee: Backlog - Query Execution
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-55062 Change stream events can exceed 16MB ... Closed
Related
related to SERVER-53387 Large internal metadata can trigger B... Backlog
Assigned Teams:
Query Execution
Participants:

 Description   

For change events with fullDocument field, the documentKey would be duplicated in the fullDocument field. If the document has large documentKey, the total size of the event would exceed the 16MB bson limit because of the duplication, and cause the change stream cursor to fail. What could be worse is that the resumeToken can also encode documentKey, resulting in more duplicates. We need to investigate approaches to mitigate this.


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