Choose the new node type, number of nodes, and other settings for the target cluster.ĥ.Review the loads from your ETL processes that occurred after you took a snapshot of the source cluster.Ħ.Stop all queries running on the source cluster. This new cluster is the target cluster.Ĥ.Resize the target cluster. The existing cluster is the source cluster.Ģ.Then, note the time that the snapshot was taken.ĭoing this means that you can later identify the point when you need to rerun extract, transact, load (ETL) processes to load any post-snapshot data into the target database.ģ.Restore the snapshot into a new cluster. The snapshot, restore, and classic resize approach uses the following process:ġ.Firstly, take a snapshot of your existing cluster. However, it minimizes the amount of time that you can’t write to the database. Then you can make the switch to the target cluster. This approach requires that any data that is written to the source cluster after the snapshot is taken must be copied manually to the target cluster after the switch.ĭepending on how long the copy takes, you might need to repeat this several times until you have the same data in both clusters. The time it takes to resize a cluster with the classic resize operation depends heavily on the amount of data in the cluster. If the resize operation is in the final stage, you can’t cancel the operation. You can cancel a classic resize operation before it completes by choosing Cancel resize from the cluster details in the Amazon Redshift console. Rows that are marked for deletion aren’t transferred, so you need to run only a VACUUM command if your tables to resort. #REDSHIFT VACUUM UPDATE#When you resize a cluster, Amazon Redshift distributes the database tables to the new nodes based on their distribution styles and runs an ANALYZE command to update statistics. You can view the resize progress on the Amazon Redshift console.Īmazon Redshift doesn’t sort tables during a resize operation, so the existing sort order is maintain. When this is complete, all connections switch to use the target cluster. Then, Amazon Redshift copies the data from the source cluster to the target cluster. It does so using the information that you specify for the node type, cluster type, and number of nodes. You can keep or delete these logs as your data policies specify.Īfter Amazon Redshift puts the source cluster into read-only mode, it provisions a new cluster, the target cluster. If you have enabled audit logging in your source cluster, you can continue to access the logs in Amazon S3. When you start the resize operation, Amazon Redshift puts the existing cluster into read-only mode until the resize finishes.ĭuring this time, you can only run queries that read from the database
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |