6.02 - Scaling Out a System After Deployment - Teradata Software for Azure

Teradata® Software for Azure Installation and Administration Guide

prodname
Teradata Software for Azure
vrm_release
6.02
category
Administration
Configuration
Installation
featnum
B035-2810-128K
  • Teradata Database downtime is required, as scaling out reconfigures the database and migrates the premium storage. Schedule a time that minimally impacts users.
  • You might need to increase Azure service limits. See Azure Service Limits.
  • Make sure each new VM has one available IP and one IP attached to an existing node from a single subnet. To allocate the required network resources, see Configuring COP Entries.
  • [BYOL only] Make sure you have enough TCores. See Bring Your Own License.
[Base, Advanced, and Enterprise tiers only] Use this procedure to scale out a system after deployment. You will receive an error if you attempt to scale out under one of the following scenarios:
  • Beyond the maximum node limit for your current system. See Supported Node Counts.
  • Beyond four times (4x) the size of a deployed 24 AMP-per-node system.
  • Beyond the minimum storage subpool count (1 per node).
  1. [Complete once per deployment] Create a service principal.
  2. Stop the database.
    # tpareset –x -f –y stop system
  3. Run the following command on all nodes to confirm the database is down.
    # pdestate -a
    PDE state: DOWN/HARDSTOP
  4. Display all supported node configurations for your current system.
    # tdc-scale-out -d
    No changes will be applied to the system.
  5. Display supported node configurations with a specific node count and any optional arguments.
    # tdc-scale-out node_count [options]
    where: This example shows how your current configuration will change after scaling out the system from 4 to 6 nodes:
    database001-01:~ # tdc-scale-out 6 -p -a 
    
    Current Configuration:
    ===========================================================================
     Nodes:
             Node Count:    4
    ---------------------------------------------------------------------------
     CPU(Core)/Mem(GB):
             CPUs/Node:    20             CPUs Total:    80
              Mem/Node:   144              Mem Total:   576
    ---------------------------------------------------------------------------
     AMPs/PEs:
             AMPs/Node:    12             AMPs Total:    48
              PEs/Node:     2              PEs Total:     8
    ===========================================================================
    
    
    Current system will be scaled out to [6]:
    ===========================================================================
     Nodes:
             Node Count:    4 => 6
    ---------------------------------------------------------------------------
     CPU(Core)/Mem(GB):
              CPUs/Node:   20 == 20       CPUs Total:    80 => 120
               Mem/Node:  144 == 144       Mem Total:   576 => 864
    ---------------------------------------------------------------------------
     AMPs/PEs:
              AMPs/Node:   12 => 8        AMPs Total:    48 == 48
               PEs/Node:    2 == 2         PEs Total:     8 => 12
    ===========================================================================
    Continue? [yes/no] yes
  6. Type yes to continue. This process takes approximately 30 minutes to complete, after which the new configuration appears under Current Configuration.
  7. [Optional] Run the following command on all nodes to confirm the database is running.
    # pdestate –a
    PDE state: RUN/STARTED
  8. [Optional] Check the diagnostic and troubleshooting logs.