Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- discovered-by-spm-4330

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
CAR Team 2026-03-02
Linked BF Score:
200
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 configureFailPoint command in passthrough tests is not compatible with multiple routers, because there is no guarantee that the failpoint will be enabled on the router that actually executes the query. In addition, the failpoint may remain enabled for subsequent tests if the command to disable it is sent to a different mongos than the one on which it was originally enabled.

is related to

SERVER-120547 MultiRouterMongo: Refer to the fail point utils introduced in SERVER-119161

Closed

SERVER-120546 MultiRouterMongo: Refer to the fail point utils introduced in SERVER-119161

Open

related to

SERVER-118479 [false alarm] Pipeline optimizations not applied if MonogS is stale

Closed

SERVER-120260 Ensure consistent failpoints even with the MultiShardedClusterFixture

Open

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

Created:: Feb 20 2026 01:34:04 PM UTC
Updated:: Mar 02 2026 11:06:26 PM UTC
Resolved:: Feb 27 2026 08:12:00 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates