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: 9.0.0-rc1
Component/s: None
Labels:
None

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
CAR Team 2026-09-14
Linked BF Score:
0
CAR Domain/s:

🟦 Shard Catalog

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

BF-46154: the createIndex state of timeseries_create_indexes.js fails with createIndexes ... conflicted with another operation after 10 retries (code 117, ConflictingOperationInProgress) in concurrency_simultaneous suites.

Since SERVER-132822 (commit 667bd4a6), createIndexes retries a NamespaceNotFound from a concurrent drop up to 10 times and then raises ConflictingOperationInProgress. Under this workload's concurrent drop/recreate that budget can legitimately be exhausted, and 117 is not in the test's tolerated codes.

Fix: accept ErrorCodes.ConflictingOperationInProgress in the createIndex state (precedents: SERVER-94610, SERVER-51522) and audit sibling FSM createIndex workloads for the same gap.

is related to

SERVER-51522 Handle ConflictingOperationInProgress errors for non-transaction createIndexes in CRUD_and_commands_with_createindexes.js

Closed

SERVER-94610 Update invalidated_cursors.js FSM test to handle additional createIndex errors

Closed

SERVER-132822 createIndexes reports success without creating the index when a concurrent moveCollection replaces the collection

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:: Sep 04 2026 01:15:47 PM UTC
Updated:: Sep 09 2026 07:52:05 AM UTC
Resolved:: Sep 09 2026 07:52:05 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty