[SERVER-67868] Use OP_MSG document sequences to serialize BatchedCommandRequests sent between nodes Created: 07/Jul/22  Updated: 05/Dec/22

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

Type: Improvement Priority: Minor - P4
Reporter: Mihai Andrei 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   

Currently, write commands that are sent between nodes (i.e. from mongos to shards or from RS secondaries to a RS primary) are serialized to BSON. This results in a lot of effort to ensure that any command that we serialize does not result in a command that goes over the maximum BSON size. One alternative to this approach is to use OP_MSG payload type 1, where the set of inserts/updates/deletes can be serialized to a document sequence. The advantage of this is that write commands can use up to 48 MiB of memory, as opposed to the 16 MB BSONObject size limit.

This ticket tracks the work to update internal clients which send write commands over the wire to leverage OP_MSG document sequences instead of serializing the entire command to BSON.


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