[SERVER-77725] make DbCheck be able to create reply message with correct SerializationContext Created: 01/Jun/23  Updated: 02/Jun/23  Resolved: 02/Jun/23

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

Type: Task Priority: Major - P3
Reporter: Sophia Tan Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Won't Do Votes: 0
Labels: ntdi_must_have
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Serverless
Participants:
Story Points: 3

 Description   

When we create a reply message for dbCheck command, we should serialize the nss according to the inputs of command request, eg, the "$tenant" and the "expectPrefix" fields, which comes from unparsed OpMsgRequest and is thread through request's serialization context to the code places where we create the reply message.

Today, the DbCheck is a BasicCommand which cannot access the unparsed request. We cannot serialize the nss correctly in reply message. 

In this ticket, we should amke the dbCheck command to be able to create the serialization context when parsing request and use the context when creating reply message.



 Comments   
Comment by Sophia Tan [ 02/Jun/23 ]

The dbCheck is not used by tenant user at all. Also, Atlas Proxy will not send dbCheck to mongod. So, we need not to serialize nss depend on "expectPrefix" of request at all. 

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