By the screenshot I can saw that you're performing resize operation in Redshift:
In resize there was node limitation handled:
There is a command in elastic resize to determine how many nodes you can edit, which is why you can only see 4 nodes throughout the resize operation. Elastic resize: If elastic resize is available as an option, use elastic resize to change the node type, number of nodes, or both. Note that when you only change the number of nodes, the queries are temporarily paused and connections are kept open. An elastic resize takes between 10-15 minutes. During a resize operation, the cluster is read-only.
To verify if your cluster is eligible for elastic resize, run the following AWS CLI or AWS CloudShell command:
aws redshift describe-node-configuration-options --cluster-identifier <cluster-id> --action-type resize-cluster
If you like increase the node more than the elastic limit you can choose classic resize: Classic resize: Use classic resize to change the node type, number of nodes, or both. Choose this option when you're resizing to a configuration that isn't available through elastic resize. A resize operation takes two hours or more, or can take up to several days depending on your data size. During the resize operation, the source cluster is read-only.
How do I resize an Amazon Redshift cluster?: https://aws.amazon.com/premiumsupport/knowledge-center/resize-redshift-cluster/
Overview of managing clusters in Amazon Redshift: https://docs.aws.amazon.com/redshift/latest/mgmt/managing-cluster-operations.html
How does elastic resize work in Amazon Redshift?: https://aws.amazon.com/premiumsupport/knowledge-center/redshift-elastic-resize/
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 3 months ago
- Why does a table in an Amazon Redshift provisioned cluster consume more or less disk storage space than expected?AWS OFFICIALUpdated 2 months ago
- EXPERTpublished 5 months ago