- Teradata Database downtime is required because scaling in reconfigures the database and migrates the EBS data volumes. Schedule a time that minimally impacts users.
- Make sure you have increased limits. Read about COP entries and make sure your system is properly configured.
Use this procedure to scale in a system after deployment.
-
[First time you scale in] Check to see if your system can be scaled in:
# tdc-scale-in -d
-
Stop the database.
# tpareset –x –y stop for scaling in
-
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. -
Enter one of the following commands to start the scale in process:
After entering one of the following commands, check log files to determine how long the process will take to finish.
The output displays how the configuration changes after the system has been scaled in, as shown in the following example:Command Description # tdc-scale-in 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-scale-in 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.
Current system will be scaled in [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: 12 => 24 AMPs Total: 48 == 48 PEs/Node: 2 == 2 PEs Total: 8 => 4 =========================================================================== Continue? [yes/no] yes - Enter yes. When the process completes, the new configuration appears under Current Configuration.
-
[Optional] Check the database status.
# pdestate –a
-
Display the Teradata system configuration to confirm the number of nodes is correct.
# tdinfo
-
If you are using Teradata DSC to run jobs, type the following command on all Teradata Database nodes to update the configuration of the media server.
# /etc/init.d/clienthandler restart-hwupgrade
- [Optional] Check the logs for troubleshooting.