-
Type:
Bug
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Sharding EMEA
-
ALL
-
(copied to CRM)
-
None
-
None
-
None
-
None
-
None
-
None
-
None
And this should remove the need to set the refresh flag in config.cache.collections. Most likely will need to keep the secondary read logic around for backwards compatibility with v4.2.
- related to
-
SERVER-42737 MongoDB stuck on update metadata
-
- Closed
-
-
SERVER-48566 Shard loader in primary nodes blindly read the version of config.cache.collections
-
- Closed
-
-
SERVER-38341 Remove Parallel Batch Writer Mutex
-
- Closed
-
-
SERVER-63847 Complete TODO listed in SERVER-44105
-
- Closed
-