-
Type: Task
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Sharding NYC
-
Sharding NYC 2022-04-18, Sharding 2022-05-02
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).