Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- former-storex-namer

Assigned Teams:

Storage Execution
Operating System:
ALL
Sprint:
Execution Team 2022-09-19, Execution Team 2024-09-02, Execution Team 2024-09-16, Execution Team 2024-09-30
Linked BF Score:
0
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

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

The call to wiredtiger alter is not transactional and will not be atomic with other writes in the same storage transaction. ~~SERVER-68186~~ implements the short term fix to reconcile inconsistent index metadata during startup. But in the long term, we should investigate if any other issues could be caused by this non-transactional update. (e.g. the storage transaction rolled back but changes to index metadata did not)

depends on

SERVER-99283 Make index data format versioning independent of uniqueness

Closed

SERVER-102910 Don't change index data format version number upon unique index conversions

Open

is related to

WT-9613 Make alter transactional with updates to other tables

Backlog

related to

SERVER-93401 Background validation sees collection documents and timeseriesBucketsMayHaveMixedSchemaData at different points in time

Blocked

SERVER-68186 Reconcile index table metadata during startup if there is a mismatch caused by collMod

Closed

SERVER-90873 Fatal Assertion: "UnsupportedFormat: Index" after running collMod forceNonUnique with stepdowns

Closed

(1 related to)

Assignee:: Unassigned
Reporter:: Yuhong Zhang
Participants:: Gregory Noma, Yuhong Zhang
Votes:: 0 Vote for this issue
Watchers:: 9 Start watching this issue

Created:: Jul 22 2022 02:02:47 AM UTC
Updated:: Mar 26 2025 03:48:35 PM UTC
Confidence Status Last Update:: 09/Jan/25 3:03 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates