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:
None

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
CAR Team 2026-01-19
Linked BF Score:
200
CAR Domain/s:

🟦 Shard Catalog

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

~~SERVER-114498~~ exposed a problem with getShardMap where in case of fixture with multiple routers the test might start with some mongos that have a shard registry not yet updated (SERVER-116303)

The cardinality_and_frequency.js uses getShardMap to determine the number of nodes. The issue described can cause the test to run with a write concern of 0 which can disrupt the test in many ways.

is related to

SERVER-116303 Investigate why getShardMap might return a stale topology on multiple mongos-es

Backlog

SERVER-114498 Integrate sharding_jscore_passthrough with the Multi-Router Mongo

Closed

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

Created:: Jan 09 2026 03:04:55 PM UTC
Updated:: Jan 12 2026 04:58:24 PM UTC
Resolved:: Jan 12 2026 04:58:24 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates