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
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
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
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
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
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
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
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
Last updated
Was this helpful?

