What are the key states to monitor for an Amazon Redshift cluster?

Resolution

The following are key cluster statuses that you can use to monitor your Amazon Redshift cluster's health, availability, and performance. 

Available

The available status occurs when the cluster is healthy, running, fully functional, and available for queries and data operations.

Modifying

The modifying status occurs when Amazon Redshift resizes the cluster, adds or removes nodes, or applies a new parameter group. The cluster is still available for read operations, but Amazon Redshift temporarily blocks or delays write operations.

For more information, see Modifying a cluster.

Deleting

The deleting status occurs while Amazon Redshift permanently deletes a cluster. Amazon Redshift doesn't perform further operations on the cluster and removes all data after the deletion process completes.

For more information, see Shutting down and deleting a cluster.

Rebooting

The rebooting status occurs when the cluster reboots its nodes because of a manual reboot request, a scheduled maintenance window, or an automatic recovery process. The cluster is unavailable during reboots, and Amazon Redshift cancels in-progress queries or operations.

For more information, see Rebooting a cluster.

Resizing

The resizing status occurs when Amazon Redshift adds or removes nodes to adjust the cluster's compute capacity. When you resize a cluster, the cluster is still available for read operations, but Amazon Redshift temporarily blocks or delays write operations.

For more information and troubleshooting, see How do I resize an Amazon Redshift cluster?

Unhealthy

The unhealthy status occurs when the cluster experiences issues that affect performance or availability. A high number of database connections, queries, incorrect parameter settings, or resource allocation might cause a cluster to become unhealthy.

Resuming

The resuming status occurs when the cluster resumes from a paused state because of inactivity after a manual or automatic pause. The cluster is still available for read operations, but Amazon Redshift temporarily blocks or delays write operations.

Paused

The paused state occurs when the you paused the cluster from connections. On-demand billing is suspended, and only the cluster's storage incurs charges. Amazon Redshift creates a snapshot and terminates all queries.

Note: If you delete a paused query and didn't request a final snapshot, then you can't restore the cluster.

For more information, see Pausing and resuming a cluster.

Maintenance

The maintenance status occurs when the cluster applies updates or performs system tasks. During the maintenance window, the cluster is still available for read operations, but Amazon Redshift temporarily blocks or delays write operations. If your cluster rebooted outside the maintenance window, then see Why did my Amazon Redshift cluster reboot outside the maintenance window?

If you can't change the maintenance track, then see Why can't I change the maintenance track for my Amazon Redshift provisioned cluster? If you scheduled maintenance but no upgrades occurred, then see Why didn't Amazon Redshift perform any upgrades during the maintenance window?

Related information

Amazon Redshift best practices