hashicorp/nomad · error

NodeDownErr

NodeDownErr

Error message

node down

What it means

Sentinel error returned by the Nomad API client when GetNodeClientWithTimeout cannot obtain an HTTP client because the target Nomad node is down or unreachable; signals the operation cannot be completed against that node.

Source

Thrown at api/allocations.go:19

// Copyright IBM Corp. 2015, 2026
// SPDX-License-Identifier: MPL-2.0

package api

import (
	"context"
	"errors"
	"io"
	"slices"
	"sort"
	"strings"
	"time"
)

var (
	// NodeDownErr marks an operation as not able to complete since the node is
	// down.
	NodeDownErr = errors.New("node down")
)

const (
	AllocDesiredStatusRun   = "run"   // Allocation should run
	AllocDesiredStatusStop  = "stop"  // Allocation should stop
	AllocDesiredStatusEvict = "evict" // Allocation should stop, and was evicted
)

const (
	AllocClientStatusPending  = "pending"
	AllocClientStatusRunning  = "running"
	AllocClientStatusComplete = "complete"
	AllocClientStatusFailed   = "failed"
	AllocClientStatusLost     = "lost"
	AllocClientStatusUnknown  = "unknown"
)

const (

View on GitHub (pinned to 482b49bf1a)

Solutions

1. Check the node's health via nomad node status and restart/reconnect the Nomad agent on that node
2. Retry the operation once the node is back in the 'ready' state
3. Route exec/alloc operations to a different healthy node if applicable

When it happens

Trigger: Thrown at api/allocations.go:19 when the library encounters an invalid state.

Common situations: See trigger scenarios.

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