Scaling In a System - Teradata Software for Azure

Teradata Vantage™ on Azure (DIY) Installation and Administration Guide

Product
Teradata Vantage on Azure
Release Number
5.01
Published
July 2018
Language
English (United States)
Last Update
2018-07-18
dita:mapPath
kmk1523992471627.ditamap
dita:ditavalPath
TeradataAzure_PubCloud_5.01_5.01.01.ditaval
dita:id
B035-2810
lifecycle
previous
Product Category
Cloud
  • Teradata Database downtime is required because scaling in reconfigures the database and migrates the premium storage. Schedule a time that minimally impacts users.
  • Increase the Azure service limits.
Use this procedure to scale in a system after deployment.
  1. Provide service principal details and enter responses to the prompts. See Azure Documentation Center for how to create the service principal.
    1. Run tdc-feature-init without arguments.
      # tdc-feature-init
    2. Enter the client ID of your service principal.
    3. Enter the secret key of your service principal.
    4. Enter the tenant of your service principal.
    5. Enter your Azure subscription ID.
    Credentials validation succeeded displays. Service principal details are written to /etc/opt/teradata/tdconfig/service_principal_config.json.
  2. [First time you scale in] Check if your system can be scaled in:
    # tdc-fold -d
  3. Stop the database.
    # tpareset –x –y stop for scaling in
  4. Verify the database is in a DOWN/HARDSTOP state.
    # pdestate -a
    PDE state: DOWN/HARDSTOP Putting the database in this state may take several minutes.
  5. Enter one of the following commands to start the scale in process: After entering one of the following commands, you can check log files to determine how long the process will take to finish.
    Command Description
    # tdc-fold 2x Removes half of the current node count.

    For example, if the current system has 8 nodes, the scaled in system will have 4 nodes.

    # tdc-fold 4x Removes a quarter of the current node count.

    For example, if the current system has 8 nodes, the scaled in system will have 2 nodes.

    The output displays how the configuration changes after scaling in the system, as shown in the following example:
    Current system will be folded by [2x]:
    ===========================================================================
     Nodes:
             Node Count:    4 => 2
    ---------------------------------------------------------------------------
     CPU(Core)/Mem(GB):
              CPUs/Node:   16 == 16       CPUs Total:   64 => 32
               Mem/Node:   65 == 65        Mem Total:  260 => 130
    ---------------------------------------------------------------------------
     AMPs/PEs:
              AMPs/Node:   10 => 20       AMPs Total:   40 == 40
               PEs/Node:    2 == 2         PEs Total:    8 => 4
    ===========================================================================
    Continue? [yes/no] yes
  6. Enter yes. When the process completes, the new configuration appears under Current Configuration.
  7. [Optional] Check the status of the database.
    # pdestate –a
  8. [Optional] Check the logs for troubleshooting.