Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 9.1.0-rc0, 9.1.0-rc1022
Affects Version/s: 9.0.0-rc0
Component/s: None
Labels:
- spm-4738-m2

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Sprint:
CAR Team 2026-07-20, CAR Team 2026-08-03, CAR Team 2026-08-17, CAR Team 2026-08-31, CAR Team 2026-09-14
Linked BF Score:
0
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

In ~~SERVER-124364~~ we made DB metadata refreshes get interrupted and retry upon setFCV, but existing concurrency jstests tests seem to rarely exercise the case where a DB refresh gets interrupted.

Add a specific concurrency test to exercise this situation. One possibiity is to extend move_primary_with_crud.js (which triggers frequent DB refreshes) to also run setFCV.

is related to

SERVER-124364 Make the full DatabaseVersionMismatch flow fully interruptible

Closed

related to

SERVER-132267 movePrimary can cause unavailability of a database due to multi-document transactions

Backlog

SERVER-132179 movePrimary and setFCV have broken assumptions in the presence of chunk migrations

Closed

SERVER-133988 Deadlock between resharding initialization, chunk migration commit, and setFCV

Closed

Assignee:: Jordi Olivares Provencio
Reporter:: Joan Bruguera Micó
Participants:: Githook User, Joan Bruguera Micó, Jordi Olivares Provencio
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: May 26 2026 10:58:59 PM UTC
Updated:: Sep 03 2026 09:18:39 AM UTC
Resolved:: Sep 03 2026 09:00:24 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty