-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.6.8, 4.0.2, 4.1.3
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
v4.0, v3.6
-
Sharding 2018-10-22, Sharding 2018-11-05, Sharding 2018-11-19, Sharding 2018-12-17
-
51
This can trigger a crash or incorrect behavior if the sharding components are accessed before being fully initialized.
One example is that the ShardServerCatalogCacheLoader is created in initializeGlobalShardingStateForMongoD before Grid::setShardingInitialized but its ReplicaSetRole member variable is initialized later in initializeShardingEnvironmentOnShardServer after Grid::setShardingInitialized. This can lead to a crash because various methods in the ShardServerCatalogCacheLoader invariant that the ReplicaSetRole will not be ReplicaSetRole::None.
An example is shown here (and the corresponding Evergreen task).
- is depended on by
-
SERVER-37330 Add sharded passthrough suites to detect errors in LogicalSessionCache
- Closed