Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.6.15, 4.0.13, 4.2.1, 4.3.1
Affects Version/s: 3.6.13, 4.0.12, 4.2.0, 4.3.1
Component/s: Sharding, Testing Infrastructure
Labels:
- sharding-wfbf-day

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.2, v4.0, v3.6
Sprint:
Sharding 2019-09-23, Sharding 2019-10-07
Linked BF Score:
14
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

We should trigger a refresh on each shard, to guarantee that shards will be aware of the config.system.sessions collection before the test starts.

is duplicated by

SERVER-43112 Sharding passthroughs that enable LogicalSessionCache refreshes should catch BackgroundOperationInProgressForDatabase and retry the operation

Closed

is related to

SERVER-44745 Trigger a logical session cache refresh for core passthrough suites using the MongoDFixture before running tests

Closed

SERVER-89126 Remove forced refreshes of the LogicalSessionCache from the test setup

Backlog

SERVER-44308 Fix call to _flushRoutingTableCacheUpdates for sessions collection in shardingtest.js

Closed

Assignee:: Alexander Taskov (Inactive)
Reporter:: Blake Oler
Participants:: Alexander Taskov, Blake Oler, Githook User
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Aug 16 2019 08:08:44 PM UTC
Updated:: Apr 09 2024 02:29:37 PM UTC
Resolved:: Sep 24 2019 06:31:56 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates