[SERVER-65003] Refactor reading default R/W concerns for config DB in catalog shard Created: 28/Mar/22  Updated: 27/Oct/23  Resolved: 21/Feb/23

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

Type: Task Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Gone away Votes: 0
Labels: sharding-nyc-subteam2, sharding-nyc-subteam2-catalog-poc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding NYC
Sprint: Sharding NYC 2022-04-18, Sharding 2022-05-02
Participants:

 Description   

Catalog shard is incapable of reading proper R/W concerns from the config server until the ServiceContext startup is complete.
However we can assume that the replica that will be elected as primary has the most recent value of the default concerns in its local config DB.

Longer term solutions:
Option 1: could be that we may need 2 step initialization - first to open the port to read the config data only, then start accepting all other commands. However maybe for default concerns this is not needed - just read them locally.
Option 2: during initialization, avoid reading the default read concern at all, supply "read local" explicitly. After initialization, block any command that needs it to read it properly (the existing code already does it).



 Comments   
Comment by Jack Mulrow [ 21/Feb/23 ]

This will be handled in SERVER-72696.

Comment by Andrew Shuvalov (Inactive) [ 16/May/22 ]

This needs verification andrew.shuvalov@mongodb.com .

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