OpenSearch snapshot-failure index_uuid: separate a name from an index incarnation
A self-consistent roundtrip is different from correct index-incarnation identity.
The actual incarnation beyond roundtrip
A self-consistent roundtrip is different from correct index-incarnation identity. Compare the failure UUID against metadata from the snapshot time. A Truthound reference copied from the current cluster could point to a recreated index; preserve the original incarnation independently. [1, 2, 3]
A semantic error hidden by string typing
OpenSearch #23299 reports SnapshotShardFailure serializing the index name into index_uuid and reading that same incorrect value back. The source analysis covers REST and repository-blob paths sharing the serializer. Decoding a string can succeed while incarnation meaning is wrong, so any corrected field value also needs a consumer-compatibility assessment. [1]
Use the historical manifest
Show a same-name recreation example, matching each failure response to snapshot-time metadata. Do not choose a recovery target using a UUID that merely repeats the name. Join snapshot manifest, index name and original UUID rather than replacing the historical reference with current metadata. [1, 3]
The difference between orders and U_old
The illustrative snapshot contains orders with UUID U_old, while its recreated index has U_new. Expected failure UUID is U_old. That passes; orders fails despite being a string, and U_new identifies another incarnation. UUID agreement alone does not establish intact snapshot contents. [1, 3]
A bounded identity-table check
Truthound Core Python SDK 3.3.2 can compare prepared snapshot_metadata_uuid and failure_index_uuid using ColumnPairValidator with relationship="==". The operator decodes the historical manifest and supplies non-missing identities. The SDK does not modify snapshot JSON or recover shards; UUID reconciliation is not a content-completeness check. [1, 2, 3]
Recovery target and recovery success
Choose recovery targets from a verified snapshot manifest and inspect clients affected by the response-value change. A name-only display may not have this incarnation obligation. Recovery also needs separate evidence that the snapshot is readable and its data reconciles. [1, 3]
Application conditions
Preserve snapshot-time metadata independently; do not substitute a current index with the same name.
Alternatives
Identify recovery targets through a verified snapshot manifest and review client compatibility with corrected values.
Limitations
The SDK does not repair snapshot JSON or shards; matching UUIDs do not establish intact data.
Evidence
- Event checked
- Subject checked
- Modified
