> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/guides/clusters/lifecycle-states-and-error-codes.md).

# Lifecycle states and error codes

The cluster lifecycle states and the customer-facing error codes, with what each means and what to do.

A cluster moves through a defined set of states, and surfaces classified error codes when something goes wrong.

## Lifecycle states

| State     | Meaning                                     | What to do                                              |
| --------- | ------------------------------------------- | ------------------------------------------------------- |
| Creating  | Initial provisioning                        | Wait                                                    |
| Running   | Active and serving queries                  | None                                                    |
| Updating  | Configuration or version change rolling out | Wait; queries continue on the current version           |
| Suspended | Zero replicas, no cost                      | Resume manually or let auto-resume handle it            |
| Resuming  | Coming back from suspension                 | Wait \~30–90 s                                          |
| Failed    | Irrecoverable error                         | Check the error code; fix and retry, or contact support |

## Error codes

When a cluster errors, e6data classifies it and tells you whether it's retryable. **Retryable** errors are recovered automatically; **terminal** errors need manual intervention.

### Startup and runtime

| Code                            | Meaning                          | Retryable | What to do                                        |
| ------------------------------- | -------------------------------- | --------- | ------------------------------------------------- |
| `E6_CLUSTER_CONTAINER_CRASHING` | Container is crash-looping       | Yes       | Check cluster logs; contact support if persistent |
| `E6_CLUSTER_OOM_KILLED`         | A component ran out of memory    | Yes       | Scale up or reduce query concurrency              |
| `E6_CLUSTER_STARTUP_TIMEOUT`    | A component didn't start in time | Yes       | Retry; check resource availability if persistent  |
| `E6_CLUSTER_INIT_FAILED`        | Initialization failed            | No        | Contact support                                   |

### Scheduling and capacity

| Code                               | Meaning                    | Retryable | What to do                               |
| ---------------------------------- | -------------------------- | --------- | ---------------------------------------- |
| `E6_CLUSTER_INSUFFICIENT_CAPACITY` | Not enough nodes available | Yes       | Wait for capacity or reduce cluster size |
| `E6_CLUSTER_QUOTA_EXCEEDED`        | Resource quota exceeded    | No        | Contact support                          |

### Image and registry

| Code                              | Meaning                             | Retryable | What to do                                   |
| --------------------------------- | ----------------------------------- | --------- | -------------------------------------------- |
| `E6_CLUSTER_IMAGE_PULL_FAILED`    | Failed to pull a container image    | Yes       | Check network; contact support if persistent |
| `E6_CLUSTER_REGISTRY_UNREACHABLE` | Cannot reach the container registry | Yes       | Check network; contact support               |

### Storage

| Code                                     | Meaning                            | Retryable | What to do                                     |
| ---------------------------------------- | ---------------------------------- | --------- | ---------------------------------------------- |
| `E6_CLUSTER_STORAGE_PROVISIONING_FAILED` | Storage volume provisioning failed | Yes       | Contact support                                |
| `E6_CLUSTER_STORAGE_PERMISSION_DENIED`   | Storage access denied              | No        | Verify storage credentials and IAM permissions |
| `E6_CLUSTER_OBJECT_STORE_UNREACHABLE`    | Cannot reach object storage        | Yes       | Check network and endpoint configuration       |

### Component availability

| Code                              | Meaning                  | Retryable | What to do                                   |
| --------------------------------- | ------------------------ | --------- | -------------------------------------------- |
| `E6_CLUSTER_PLANNER_UNAVAILABLE`  | Query planner is down    | Yes       | May self-heal; check activity history        |
| `E6_CLUSTER_QUEUE_UNAVAILABLE`    | Queue manager is down    | Yes       | May self-heal; check activity history        |
| `E6_CLUSTER_EXECUTOR_UNAVAILABLE` | No executors available   | Yes       | Check scaling settings and node availability |
| `E6_CLUSTER_EXECUTOR_DEGRADED`    | Some executors unhealthy | Yes       | Queries still run with reduced performance   |

### Configuration and credentials

| Code                               | Meaning                          | Retryable | What to do                                      |
| ---------------------------------- | -------------------------------- | --------- | ----------------------------------------------- |
| `E6_CLUSTER_CONFIGURATION_MISSING` | Required configuration not found | No        | Check cluster configuration; recreate if needed |
| `E6_CLUSTER_CONFIG_INVALID`        | Invalid configuration            | No        | Review and correct the cluster settings         |
| `E6_CLUSTER_CREDENTIALS_INVALID`   | Invalid credentials              | No        | Update storage or service credentials           |
| `E6_CLUSTER_TENANT_CONFIG_INVALID` | Workspace configuration issue    | No        | Contact your admin or support                   |

## See also

* [Troubleshooting clusters](/query-engine/guides/clusters/troubleshooting-clusters.md)
* [Create and manage clusters](/query-engine/guides/clusters/create-and-manage-clusters.md)
* [Cluster states (reference)](/query-engine/reference/cluster-reference/cluster-states.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/guides/clusters/lifecycle-states-and-error-codes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.