Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 9.1.0-rc0, 9.1.0-rc1022
Affects Version/s: None
Component/s: None
Labels:
- bkp

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v9.0
Sprint:
CAR Team 2026-09-14
Linked BF Score:
0
CAR Domain/s:
None

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

The collmod command is known to not return the same values after a retry (see SERVER-48397 and SERVER-132818). This means that if a shard retries internally, the response will be different, which breaks the requirements of this test.

This is something that we plan to address in a future project, so for now we will exclude that test from stepdown suites.

is related to

SERVER-132818 Collmod command response in sharded cluster is dependent on whether a retry occurs

Backlog

SERVER-48397 Make collMod no-op behaviour consistent

Needs Scheduling

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

Created:: Sep 08 2026 07:32:10 AM UTC
Updated:: Sep 20 2026 11:17:35 AM UTC
Resolved:: Sep 08 2026 03:25:34 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty