On the other hand, you might choose another Availability Zone for higher availability. Amazon Redshift
may not be available in all Availability Zones within a region
Modifying a Cluster
From time to time after your cluster is running, you will probably want to make changes to it. For example,
you might associate a different parameter group with it, associate another list of security groups to include
additional security groups, or revoke existing security group associations.
When you associate a new parameter group, you must reboot the cluster for the change to take effect.
You can immediately reboot the cluster by using the Amazon API or the Amazon Redshift console. If
Amazon Redshift reboots the cluster during maintenance operations, the new parameter group will take
effect.
When you change the security group associations for a cluster, a reboot is not required.
Resizing a Cluster
If your storage and performance needs change after you initially provision your cluster, you can always
scale the cluster in or out by adding or removing nodes. Additionally, you can scale the cluster up or down
by specifying a different node type.When using the API you have to specify both even if you are only
changing one. Resizing the cluster in either way involves minimal downtime
When you resize a cluster, Amazon Redshift first puts your existing cluster in the read-only mode. Amazon
Redshift then provisions the nodes as requested, copies data to the new cluster, and switches your
connections to use the new cluster. At this time you lose any open connections to the old cluster. If you
have any queries in progress at the time of this switch, you will notice the connection loss.You must
restart the query on the new cluster.
In a modify operation, you can resize your cluster as necessary. For example, you can add more nodes,
change the node types, change single-node cluster to multinode or a multinode cluster to a single-node.
You must, however, ensure that the resulting cluster is large enough to hold the data that you currently
have; otherwise the resize will fail.
Cluster Maintenance
Amazon Redshift periodically performs maintenance to apply upgrades to your cluster. During these
updates, your Amazon Redshift cluster will not be available for normal operations.You can schedule a
thirty-minute weekly maintenance window during which these activities will take place.You can set the
maintenance window when you create the cluster, or you can modify the maintenance window whenever
you want.You can set the maintenance window either programmatically or by using the Amazon Redshift
console.While Amazon Redshift is performing maintenance, it will terminate any queries or other operations
that are in progress. If there are no maintenance tasks to perform during the scheduled maintenance
window, your cluster continues to operate normally until the next maintenance window.
Supported Platforms to Launch Your Cluster
Depending on your AWS account settings, you can launch an Amazon Redshift cluster on one of the
following Amazon Elastic Compute Cloud (EC2) platforms:
• EC2-Classic – Your cluster runs in a single, flat network that you share with other AWS customers.
If you deploy on EC2-Classic, you will control access to your cluster by associating one or more Amazon
Redshift cluster security groups with the cluster. For more information, see Amazon Redshift Cluster
Security Groups (p. 32).
API Version 2012-12-01
6
Amazon Redshift Management Guide
Modifying a Cluster
To Next Page
Loading...
Need help?
General
