Test that a 3.4 feature compatibility version mixed shard replica sets behave as v3.4 servers, then smoothly transition to 3.6 feature compatibility operation. In 3.4 fcv, orphans should be readable on secondaries. Once 3.6 fcv is set, secondaries should not need to refresh remotely, but should just start working.
The profiler might be useful for testing: https://github.com/mongodb/mongo/blob/master/jstests/libs/profiler.js
- has to be done after
-
SERVER-30148 Move force primary refresh functionality out of the ShardServerCatalogCacheLoader into the ShardingState's refresh logic
-
- Closed
-
-
-
- Closed
-