-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
2
The first LogicalSessionCache refresh on a shard causes a background index build on the sessions collection. With periodic refreshes of LogicalSessionCache enabled, this can lead to errors when operations that cannot tolerate background index builds are executed.
In order to resolve this issue, SERVER-42866 and SERVER-44745 introduced forced refreshes of the LogicalSessionCache during setup of the test fixture. This ensures that all shards have refreshed their CatalogCache at least once before running the tests, so that the indexes are already built. However, this approach is not representative of user workflows, such that the implementation of a different solution should be explored.
- related to
-
SERVER-43112 Sharding passthroughs that enable LogicalSessionCache refreshes should catch BackgroundOperationInProgressForDatabase and retry the operation
- Closed
-
SERVER-44745 Trigger a logical session cache refresh for core passthrough suites using the MongoDFixture before running tests
- Closed
-
SERVER-87320 Logical session cache refresh during test setup is not guaranteed to fetch up to date information
- Closed
-
SERVER-42866 Trigger a logical session cache refresh on all shards in the ShardedCluster test fixture before running test
- Closed