-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 7.2.0-rc0, 7.0.2, 7.1.0
-
Component/s: None
-
Labels:
-
Fully Compatible
-
ALL
-
v7.1, v7.0
-
Sharding EMEA 2023-10-30
-
120
-
2
During assertIsPrimaryShardForDb, it may happen that the node’s cached database info is cleared. Therefore, we must not assume that _dbInfo from the dss is always set:
const auto primaryShardId = scopedDss->_dbInfo->getPrimary();
The goal of this ticket is to guarantee that is safe accessing the node's cached db info in order to check if the node is the db primary node.
- is caused by
-
SERVER-72869 Push the database metadata from the Storage Catalog back to the Database Sharding State
-
- Closed
-