Teradata Database downtime is required, as scaling in reconfigures the database and migrates the premium storage. Schedule a time that minimally impacts users.
[Base, Advanced, and Enterprise tiers only] Use this procedure to scale in a system after deployment. If you attempt to scale in under one of the following scenarios, you will receive an error:
- Beyond the base number of nodes you originally deployed.
- Beyond the maximum storage subpool count (8 per node).
- [Complete once per deployment] Create a service principal.
-
Stop the database.
# tpareset –x -f –y stop system -
Run the following command on all nodes to confirm the database is down.
# pdestate -a
PDE state: DOWN/HARDSTOP -
Display all supported node configurations for your current system.
# tdc-scale-in -d
No changes will be applied to the system. -
Run tdc-scale-in node_count [options].
where:
- node_count is the number of nodes to which you want to scale in.
- [options] might include -a, -n, or -p. See Optional Arguments for Scaling Out or Scaling In.
database001-01:~ # tdc-scale-in 4 -a -p Current Configuration: =========================================================================== Nodes: Node Count: 6 --------------------------------------------------------------------------- CPU(Core)/Mem(GB): CPUs/Node: 20 CPUs Total: 120 Mem/Node: 144 Mem Total: 864 --------------------------------------------------------------------------- AMPs/PEs: AMPs/Node: 8 AMPs Total: 48 PEs/Node: 2 PEs Total: 12 =========================================================================== Current system will be scaled out by [6]: =========================================================================== Nodes: Node Count: 6 => 4 --------------------------------------------------------------------------- CPU(Core)/Mem(GB): CPUs/Node: 20 == 20 CPUs Total: 120 => 80 Mem/Node: 144 == 144 Mem Total: 864 => 576 --------------------------------------------------------------------------- AMPs/PEs: AMPs/Node: 8 => 12 AMPs Total: 48 == 48 PEs/Node: 2 == 2 PEs Total: 12 => 8 =========================================================================== Continue? [yes/no] yes - Type yes to continue. This process takes approximately 30 minutes to complete, after which the new configuration appears under Current Configuration.
-
[Optional] Run the following command on all nodes to confirm the database is running.
# pdestate –a
PDE state: RUN/STARTED - [Optional] Check the diagnostic and troubleshooting logs.