-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
v4.4
-
Sharding 2020-03-23, Sharding 2020-04-06
-
11
This parallels SERVER-42866 and SERVER-44308 that are adding a fix for the ShardedClusterFixture and ShardingTest. There are also failures in the logical_session_cache_standalone_*sec_refresh_jscore_passthrough.yml suites running on standalones.
A test running a restartCatalog cmd is running into an index-build-in-progress error due to an index being created on the sessions collection.
- causes
-
SERVER-87320 Logical session cache refresh during test setup is not guaranteed to fetch up to date information
-
- Closed
-
- depends on
-
SERVER-47043 Read concern set to default when it should be local
-
- Closed
-
- is related to
-
SERVER-89126 Remove forced refreshes of the LogicalSessionCache from the test setup
-
- Backlog
-
- related to
-
SERVER-42866 Trigger a logical session cache refresh on all shards in the ShardedCluster test fixture before running test
-
- Closed
-
-
SERVER-44308 Fix call to _flushRoutingTableCacheUpdates for sessions collection in shardingtest.js
-
- Closed
-