hashicorp/nomad · critical

index update failed: %w

Error message

index update failed: %w

What it means

Wraps a txn.Insert failure while updating the index table entry for TableTaskGroupHostVolumeClaim after a successful claim deletion. Without the index bump, blocking queries for this table would not fire, so the transaction aborts and the claim remains. Indicates low-level store problems rather than user error.

Source

Thrown at nomad/state/state_store_task_group_volume_claims.go:209

	obj, err := txn.First(TableTaskGroupHostVolumeClaim, indexClaimID, claimID)
	if err != nil {
		return fmt.Errorf("task group volume claim lookup failed: %v", err)
	}

	if obj == nil {
		return errors.New("task group volume claim does not exist")
	}
	claim := obj.(*structs.TaskGroupHostVolumeClaim)
	if claim.Namespace != ns {
		return errors.New("task group volume claim does not exist")
	}

	if err := txn.Delete(TableTaskGroupHostVolumeClaim, obj); err != nil {
		return err
	}

	if err := txn.Insert(tableIndex, &IndexEntry{TableTaskGroupHostVolumeClaim, index}); err != nil {
		return fmt.Errorf("index update failed: %w", err)
	}

	return txn.Commit()
}

func (s *StateStore) updateStickyVolumeClaimsFromAlloc(txn *txn, index uint64, alloc *structs.Allocation) error {
	var node *structs.Node
	var err error
	tg := alloc.Job.LookupTaskGroup(alloc.TaskGroup)
	if tg != nil {
		for _, req := range tg.Volumes {
			if !req.Sticky {
				continue
			}
			if node == nil {
				node, err = s.NodeByID(nil, alloc.NodeID)
				if err != nil {
					return err

View on GitHub (pinned to 482b49bf1a)

Solutions

1. Retry the claim deletion
2. Examine the wrapped (%w) memdb error in server logs
3. Restart the Nomad server to rebuild in-memory state from Raft
4. Restore from a known-good Raft snapshot or upgrade Nomad if corruption recurs

if err := deleteClaim(claimID); err != nil {
    if strings.Contains(err.Error(), "index update failed") {
        return retryAfterBackoff()
    }
    return err
}

When it happens

Trigger: Calling DeleteTaskGroupHostVolumeClaim when the index-entry insert fails after txn.Delete succeeded; the error is returned via applyTaskGroupHostVolumeClaimDelete.

Common situations: Corrupted index tables; Nomad internal bugs; unhealthy or resource-starved servers; usually clustered with other state-store errors.

Related errors

• index update failed: %v
• index update failed: %v
• Task group volume claim insert failed: %v
• index update failed: %v
• Task group volume claim lookup failed: %v

AI-assisted analysis of hashicorp/nomad@482b49bf1a (2026-09-04). Data as JSON: /api/errors/0418233feef0e0fe. Report an issue: GitHub.