Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Sprint:
CAR Team 2026-02-16
CAR Domain/s:

🟩 Routing and Topology

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

The self-test should just ensure we are using a multi-router once 2 or more mongos are detected.
Place the self-test within the core/ folder to ensure it's executed by every suite

is depended on by

SERVER-119522 Investigate why timeseries_update_arbitrary_updates_not_enabled.js fails on multi-router

In Progress

related to

SERVER-119259 Investigate why explain might rarely reports 2 different result when run against 2 different routers

Backlog

SERVER-119522 Investigate why timeseries_update_arbitrary_updates_not_enabled.js fails on multi-router

In Progress

Assignee:: Enrico Golfieri
Reporter:: Enrico Golfieri
Participants:: Enrico Golfieri, Githook User
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Feb 05 2026 02:33:38 PM UTC
Updated:: Feb 12 2026 04:10:07 PM UTC
Resolved:: Feb 12 2026 04:03:37 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates