Resizing an Instance

Prerequisite
Before starting, ask your IAM administrator to grant you the ec2:ModifyInstanceAttribute permission so you can resize an instance.
You must stop an instance before you can change the instance type. You should resize only supported instance types as described in Teradata Database EBS Storage.
Note
If you resize to unsupported instance types, database performance may be impacted. Data loss will occur if resizing local storage instance types.

Resizing has no affect on Teradata software that is running on an instance.

For additional information, see Amazon User Guide for Linux Instances and search for Resizing an Amazon EBS-backed Instance.

  1. Stop the database on a single instance in the system.
    # tpareset -x stop system
    It may take a few minutes to put the database in this state.
  2. Wait for the database to shut down.
    # psh pdestate -w
    PDE state: DOWN/HARDSTOP
  3. If you are changing an instance type to or from m4.16xlarge, do the following on a single instance in the system to remove the 70-persistent-net.rules file from all nodes:
    This step is required in order to connect to the node after the m4.16xlarge instance type is resized.
    1. Type the following:
      # psh rm /etc/udev/rules.d/70-persistent-net.rules
    2. When asked to confirm, type y.
      The 70-persistent-net.rules file is regenerated when the instance starts.
  4. Do one of the following to stop all instances at the same time.
    Option Actions
    Using the command line On a single instance in the system:
    1. # psh init 0
    Using the AWS EC2 Console
    1. In the navigation pane, click Running Instances.
    2. Select the check box next to all instances.
    3. Select Actions > Instance State > Stop.
    4. In the confirmation box, click Yes, Stop.

      It may take a few minutes for the instances to stop.

  5. From the AWS EC2 Console, select the check box next to all instances.
  6. Select Actions > Instance Settings > Change Instance Type.
  7. Select the EBS-optimized check box which enables EBS optimization.
  8. Click Apply.
  9. From the AWS EC2 Console, select the check box next to all instances.
  10. Select Actions > Instance State > Start.
  11. In the confirmation box, click Yes, Start.
    It may take a few minutes for the instances to start.
    If you did not change the default Teradata Database start behavior, all instances start and the Teradata Database returns to a running state.

results matching ""

    No results matching ""