Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Trivial - P5
Fix Version/s: 8.1.0-rc0
Affects Version/s: None
Component/s: Sharding
Labels:

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Cluster Scalability 2024-6-10, Cluster Scalability 06/24/24
Confidence Status:
None
Work Order:
3

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

After ~~SERVER-41193~~, the refreshSessionsInternal command no longer exists. However, it's still mentioned in:

jstests/sharding/read_write_concern_defaults_application.js
jstests/sharding/safe_secondary_reads_single_migration_suspend_range_deletion.js
jstests/sharding/safe_secondary_reads_single_migration_waitForDelete.js
jstests/sharding/database_versioning_all_commands.js
jstests/sharding/safe_secondary_reads_drop_recreate.js

is caused by

SERVER-41193 Get rid of the `refreshSessionsInternal` command

Closed

Assignee:: Chris Castillo (Inactive)
Reporter:: A. Jesse Jiryu Davis
Participants:: A. Jesse Jiryu Davis, Chris Castillo, Githook User
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: Sep 28 2020 05:20:07 PM UTC
Updated:: Nov 19 2024 05:24:00 AM UTC
Resolved:: Jun 14 2024 05:07:13 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates