-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Sharding
-
ALL
Starting in 3.6, when a shard mongod loads the chunk metadata for a sharded collection, it records that metadata durably. If the mongod restarts, however, the in-memory cache of that information is lost and isn't loaded until a metadata refresh is triggered via a request from a mongos. Shard mongods should load the routing information from its persistent local copy into memory at startup.
- duplicates
-
SERVER-32198 Missing collection metadata on the shard implies both UNSHARDED and "metadata not loaded yet"
- Closed
- related to
-
SERVER-32198 Missing collection metadata on the shard implies both UNSHARDED and "metadata not loaded yet"
- Closed