AWS redshift documentation change
Summary
Added documentation for new RG node type in Redshift cluster resizing operations, including upgrade paths, elastic resize capabilities, constraints, and monitoring procedures.
Security assessment
The changes introduce documentation for RG node type alongside existing RA3 nodes. Updates cover operational aspects like resizing limits, node conversion warnings, and backup behaviors during elastic resize. No security vulnerabilities, exploits, or security-specific features are mentioned. Changes are feature-expansion focused.
Diff
diff --git a/redshift/latest/mgmt/resizing-cluster.md b/redshift/latest/mgmt/resizing-cluster.md index d97140074..8af1e7745 100644 --- a//redshift/latest/mgmt/resizing-cluster.md +++ b//redshift/latest/mgmt/resizing-cluster.md @@ -36 +36 @@ For more information about resizing clusters, including walking through the proc -If you have reserved nodes, you can upgrade to RA3 reserved nodes. You can do this when you use the console to restore from a snapshot or to perform an elastic resize. You can use the console to guide you through this process. For more information about upgrading to RA3 nodes, see [Upgrading to RA3 node types](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html#rs-upgrading-to-ra3). +If you have reserved nodes, you can upgrade to RG or RA3 reserved nodes. You can do this when you use the console to restore from a snapshot or to perform an elastic resize. You can use the console to guide you through this process. For more information about upgrading to RG node types, see [Upgrading to RG node types](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html#rs-upgrading-to-rg). For more information about upgrading to RA3 nodes, see [Upgrading to RA3 node types](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html#rs-upgrading-to-ra3). @@ -44 +44 @@ A resize operation comes in two types: - * **Elastic resize** – You can add nodes to or remove nodes from your cluster. You can also change the node type, such as from DC2 nodes to RA3 nodes. An elastic resize typically completes quickly, taking ten minutes on average. For this reason, we recommend it as a first option. When you perform an elastic resize, it redistributes data slices, which are partitions that are allocated memory and disk space in each node. Elastic resize is appropriate when you: + * **Elastic resize** – You can add nodes to or remove nodes from your cluster. You can also change the node type, such as from DC2 nodes to RG or RA3 nodes. An elastic resize typically completes quickly, taking ten minutes on average. For this reason, we recommend it as a first option. When you perform an elastic resize, it redistributes data slices, which are partitions that are allocated memory and disk space in each node. Elastic resize is appropriate when you: @@ -68 +68 @@ An elastic resize operation, when you add or remove nodes of the same type, has - 1. Elastic resize takes a cluster snapshot. No-backup tables are only supported for DC2 nodes. For all other types of cluster, no-backup tables are included in the snapshot. For more information, see [Excluding tables from snapshots](./working-with-snapshots.html#snapshots-no-backup-tables). If your cluster doesn't have a recent snapshot, because you disabled automated snapshots, the backup operation can take longer. (To minimize the time before the resize operation begins, we recommend that you enable automated snapshots or create a manual snapshot before starting the resize.) When you start an elastic resize and a snapshot operation is in progress, the resize can fail if the snapshot operation doesn't complete within a few minutes. For more information, see [Amazon Redshift snapshots and backups](./working-with-snapshots.html). + 1. Elastic resize takes a cluster snapshot. No-backup tables are only supported for DC2 nodes. For RG and RA3 clusters no-backup tables are included in the snapshot. For more information, see [Excluding tables from snapshots](./working-with-snapshots.html#snapshots-no-backup-tables). If your cluster doesn't have a recent snapshot, because you disabled automated snapshots, the backup operation can take longer. (To minimize the time before the resize operation begins, we recommend that you enable automated snapshots or create a manual snapshot before starting the resize.) When you start an elastic resize and a snapshot operation is in progress, the resize can fail if the snapshot operation doesn't complete within a few minutes. For more information, see [Amazon Redshift snapshots and backups](./working-with-snapshots.html). @@ -85 +85 @@ It's unlikely that an elastic resize would fail. However, in the case of a failu -If you have reserved nodes, for example DC2 reserved nodes, you can upgrade to RA3 reserved nodes when you perform a resize. You can do this when you perform an elastic resize or use the console to restore from a snapshot. The console guides you through this process. For more information about upgrading to RA3 nodes, see [Upgrading to RA3 node types](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html#rs-upgrading-to-ra3). +If you have reserved nodes, for example DC2 reserved nodes, you can upgrade to RA3 reserved nodes when you perform a resize. You can do this when you perform an elastic resize or use the console to restore from a snapshot. The console guides you through this process. For more information about upgrading to RG node types, see [Upgrading to RG node types](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html#rs-upgrading-to-rg). For more information about upgrading to RA3 nodes, see [Upgrading to RA3 node types](https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html#rs-upgrading-to-ra3). @@ -101 +101 @@ Elastic resize has the following constraints: -The following example CLI command describes the configuration options available. In this example, the cluster named `mycluster` is a `dc2.large` 8-node cluster. +The following example CLI command describes the configuration options available. In this example, the cluster named `mycluster` is a `rg.4xl` 8-node cluster. @@ -107 +107 @@ This command returns an option list with recommended node types, number of nodes - * _Ceiling on additional nodes_ \- Elastic resize has limits on the nodes that you can add to a cluster. For example, a dc2 cluster supports elastic resize up to double the number of nodes. To illustrate, you can add a node to a 4-node dc2.8xlarge cluster to make it a five-node cluster, or add more nodes until you reach eight. + * _Ceiling on additional nodes_ \- Elastic resize has limits on the nodes that you can add to a cluster. For example, a RG or RA3 cluster supports elastic resize up to four times the number of nodes. To illustrate, you can add a node to a 4-node rg.4xl cluster to make it a five-node cluster, or add more nodes until it reaches sixteen. @@ -113 +113 @@ The growth and reduction limits are based on the original node type and the numb -With some ra3 node types, you can increase the number of nodes up to four times the existing count. Specifically, suppose that your cluster consists of ra3.4xlarge or ra3.16xlarge nodes. You can then use elastic resize to increase the number of nodes in an 8-node cluster to 32. Or you can pick a value below the limit. (Keep in mind that the ability to grow the cluster by 4x depends on the source cluster size.) If your cluster has ra3.xlplus nodes, the limit is double. +With some rg and ra3 node types, you can increase the number of nodes up to four times the existing count. Specifically, suppose that your cluster consists of ra3.4xlarge or ra3.16xlarge nodes. You can then use elastic resize to increase the number of nodes in an 8-node cluster to 32. Or you can pick a value below the limit. (Keep in mind that the ability to grow the cluster by 4x depends on the source cluster size.) If your cluster has ra3.xlplus nodes, the limit is double. @@ -115 +115 @@ With some ra3 node types, you can increase the number of nodes up to four times -All ra3 node types support a decrease in the number of nodes to a quarter of the existing count. For example, you can decrease the size of a cluster with ra3.4xlarge nodes from 12 nodes to 3, or to a number above the minimum. +All rg and ra3 node types support a decrease in the number of nodes to a quarter of the existing count. For example, you can decrease the size of a cluster with ra3.4xlarge nodes from 12 nodes to 3, or to a number above the minimum. @@ -120,0 +121,2 @@ Original node type | Growth limit | Reduction limit +rg.4xlarge | 4x | To one quarter of the number +rg.xlarge | 2x | To one half of the number @@ -130 +132 @@ dc2.large | 2x | To one half of the number -**Choosing legacy node types when you resize an RA3 cluster** – If you attempt to resize from a cluster with RA3 nodes to another node type, such as DC2 , a validation warning message appears in the console, and the resize operation won't complete. This occurs because resize to legacy node types isn't supported. This is to prevent a customer from resizing to a node type that's deprecated or soon to be deprecated. This applies for both elastic resize and classic resize. +**Choosing legacy node types when you resize an RG or RA3 cluster** – If you attempt to resize from a cluster with RG or RA3 nodes to another node type, such as DC2 , a validation warning message appears in the console, and the resize operation won't complete. This occurs because resize to legacy node types isn't supported. This is to prevent a customer from resizing to a node type that's deprecated or soon to be deprecated. This applies for both elastic resize and classic resize. @@ -139 +141 @@ Classic resize handles use cases where the change in cluster size or node type i -### Classic resize to RA3 can provide better availability +### Classic resize to RG or RA3 can provide better availability @@ -141 +143 @@ Classic resize handles use cases where the change in cluster size or node type i -Classic resize has been enhanced when the target node type is RA3. It does this by using a backup and restore operation between the source and target cluster. When the resize begins, the source cluster restarts and is unavailable for a few minutes. After that, the cluster is available for read and write operations while the resize continues in the background. +Classic resize has been enhanced when the target node type is RG or RA3. It does this by using a backup and restore operation between the source and target cluster. When the resize begins, the source cluster restarts and is unavailable for a few minutes. After that, the cluster is available for read and write operations while the resize continues in the background. @@ -145 +147 @@ Classic resize has been enhanced when the target node type is RA3. It does this -To ensure you have the best performance and results when you perform a classic resize to an RA3 cluster, complete this checklist. When you don't follow the checklist, you may not get some of the benefits of classic resizing with RA3 nodes, such as the ability to do read and write operations. +To ensure you have the best performance and results when you perform a classic resize to an RG or RA3 cluster, complete this checklist. When you don't follow the checklist, you may not get some of the benefits of classic resizing with RG or RA3 nodes, such as the ability to do read and write operations. @@ -166 +168 @@ The `svv_table_info` table is visible only to superusers. -#### Sorting and distribution operations that result from classic resize to RA3 +#### Sorting and distribution operations that result from classic resize to RG or RA3 @@ -168 +170 @@ The `svv_table_info` table is visible only to superusers. -During classic resize to RA3, tables with KEY distribution that are migrated as EVEN distribution are converted back to their original distribution style. The duration of this is dependent on the size of the data and how busy your cluster is. Query workloads are given higher priority to run over data migration. For more information, see [Distribution styles](https://docs.aws.amazon.com/redshift/latest/dg/c_choosing_dist_sort.html). Both reads and writes to the database work during this migration process, but it can take longer for queries to complete. However, concurrency scaling can boost performance during this time by adding resources for query workloads. You can see the progress of data migration by viewing results from the [SYS_RESTORE_STATE](https://docs.aws.amazon.com/redshift/latest/dg/SYS_RESTORE_STATE.html) and [SYS_RESTORE_LOG](https://docs.aws.amazon.com/redshift/latest/dg/SYS_RESTORE_LOG.html) views. More information about monitoring follows. +During classic resize to RG or RA3, tables with KEY distribution that are migrated as EVEN distribution are converted back to their original distribution style. The duration of this is dependent on the size of the data and how busy your cluster is. Query workloads are given higher priority to run over data migration. For more information, see [Distribution styles](https://docs.aws.amazon.com/redshift/latest/dg/c_choosing_dist_sort.html). Both reads and writes to the database work during this migration process, but it can take longer for queries to complete. However, concurrency scaling can boost performance during this time by adding resources for query workloads. You can see the progress of data migration by viewing results from the [SYS_RESTORE_STATE](https://docs.aws.amazon.com/redshift/latest/dg/SYS_RESTORE_STATE.html) and [SYS_RESTORE_LOG](https://docs.aws.amazon.com/redshift/latest/dg/SYS_RESTORE_LOG.html) views. More information about monitoring follows. @@ -181 +183 @@ For more information about automatic table vacuum, see [Vacuuming tables](https: -#### Classic resize steps when the target cluster is RA3 +#### Classic resize steps when the target cluster is RG or RA3 @@ -183 +185 @@ For more information about automatic table vacuum, see [Vacuuming tables](https: -Classic resize consists of the following steps, when the target cluster type is RA3 and you've met the prerequisites detailed in the previous section. +Classic resize consists of the following steps, when the target cluster type is RG or RA3 and you've met the prerequisites detailed in the previous section. @@ -189 +191 @@ Classic resize consists of the following steps, when the target cluster type is - 3. Data is migrated to the target cluster. When the target node type is RA3, reads and writes are available during data migration. + 3. Data is migrated to the target cluster. When the target node type is RG or RA3, reads and writes are available during data migration. @@ -202 +204 @@ You can view the resize progress on the Amazon Redshift console. The time it tak -**Choosing legacy node types when you resize an RA3 cluster** – If you attempt to resize from a cluster with RA3 nodes to another node type, such as DC2 , a validation warning message appears in the console, and the resize operation won't complete. This occurs because resize to legacy node types isn't supported. This is to prevent a customer from resizing to a node type that's deprecated or soon to be deprecated. This applies for both elastic resize and classic resize. +**Choosing legacy node types when you resize an RG or RA3 cluster** – If you attempt to resize from a cluster with RG or RA3 nodes to another node type, such as DC2 , a validation warning message appears in the console, and the resize operation won't complete. This occurs because resize to legacy node types isn't supported. This is to prevent a customer from resizing to a node type that's deprecated or soon to be deprecated. This applies for both elastic resize and classic resize. @@ -204 +206 @@ You can view the resize progress on the Amazon Redshift console. The time it tak -#### Monitoring a classic resize when the target cluster is RA3 +#### Monitoring a classic resize when the target cluster is RG or RA3 @@ -210 +212 @@ Drop tables that you don't need when you perform a classic resize. When you do t -### Classic resize steps when the target cluster isn't RA3 +### Classic resize steps when the target cluster isn't RG or RA3 @@ -212 +214 @@ Drop tables that you don't need when you perform a classic resize. When you do t -Classic resize consists of the following, when the target node type is anything other than RA3, like DC2, for instance. +Classic resize consists of the following, when the target node type is anything other than RG or RA3, like DC2, for instance. @@ -233 +235 @@ You can view the resize progress on the Amazon Redshift console. The time it tak -It can take days or possibly weeks to resize a cluster with a large amount of data when the target cluster isn't RA3, or it doesn't meet the prerequisites for an RA3 target cluster detailed in the previous section. +It can take days or possibly weeks to resize a cluster with a large amount of data when the target cluster isn't RG or RA3, or it doesn't meet the prerequisites for an RA3 target cluster detailed in the previous section. @@ -246 +248 @@ Behavior | Elastic resize | Classic resize | Comments -**Cancelling a resize operation** | You can't cancel an elastic resize. | You can cancel a classic resize operation before it completes by choosing **Cancel resize** from the cluster details in the Amazon Redshift console. | The amount of time it takes to cancel a resize depends on the stage of the resize operation when you cancel. When you do this, the cluster isn't available until the cancel operation completes. If the resize operation is in the final stage, you can't cancel. For classic resize to an RA3 cluster, you can't cancel. +**Cancelling a resize operation** | You can't cancel an elastic resize. | You can cancel a classic resize operation before it completes by choosing **Cancel resize** from the cluster details in the Amazon Redshift console. | The amount of time it takes to cancel a resize depends on the stage of the resize operation when you cancel. When you do this, the cluster isn't available until the cancel operation completes. If the resize operation is in the final stage, you can't cancel. For classic resize to an RG or RA3 cluster, you can't cancel.