Loading...

XML

Word

Printable

JSON

Details

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 7.0.0-rc0, 6.0.9
Affects Version/s: None
Component/s: Aggregation Framework
Labels:
None

Assigned Teams:

Query Execution
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Case:

Description

Each document is limited to 16MB, but because a change event can be required to report both the document after the update and also the update description, we can easily exceed 16MB.

For example, this can be reproduced with the following:
1. Insert a 10 million character string into the DB
2. Update the document to include a different 10 million character string

Attachments

Issue Links

is duplicated by

SERVER-64592 Make sure events with large documentKey do not crash change stream

Closed

is related to

SERVER-81295 Cannot resume V2 changeStream pipelines with V1 resume tokens

Closed

SERVER-67699 Add tracking for when change stream event exceeds 16Mb

Closed

KAFKA-247 Recreate change stream from the point of failure for event > 16 MB

Closed

related to

SERVER-53387 Large internal metadata can trigger BSONObjectTooLarge for commands under the BSON size limit

Backlog

KAFKA-381 Support change stream split large events

Backlog

(1 related to)

Activity

People

Assignee:: Backlog - Query Execution

Reporter:: Charlie Swanson

Participants:: Alex Svatukhin, Backlog - Query Execution, Bernard Gorman, Charlie Swanson, Gatsby Lee, Katya Kamenieva, Palani Thangaraj, Yue Wang

Votes:: 7 Vote for this issue

Watchers:: 51 Start watching this issue

Dates

Created:: Mar 09 2021 03:38:00 PM UTC

Updated:: Nov 21 2023 11:40:39 AM UTC

Resolved:: Apr 17 2023 06:11:23 PM UTC