- Teradata Database downtime is required because scaling out reconfigures the database and migrates the EBS data volumes. Schedule a time that minimally impacts users.
- Make sure you increased limits. Read about COP entries and make sure your system is properly configured.
- Create a new system image if a previous restore image was generated or if you have upgraded software since deploying an instance that you are scaling out.
- For BYOL, make sure you have enough TCores before you scale out the system.
Use this procedure for any of the following:
- If you did not initially scale out a system during deployment
- If you previously scaled out a system during deployment and want to scale out again after deployment
It takes about 20 minutes for a 2-node system and 30 minutes for a 4-node system, depending on the number of EBS volumes and AWS provisioning time.
-
[First time you scale out] Check if your system can be scaled out:
# tdc-scale-out -d
-
Stop the database.
# tpareset –x –y stop for scaling out
-
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 out process:
The output displays how the configuration changes after scaling out the system, as shown in the following example:Command Description # tdc-scale-out 2x Doubles the current node count. For example, if the current system has 4 nodes, the scaled out system will have 8 nodes.
# tdc-scale-out 4x Quadruples the current node count. For example, if the current system has 4 nodes, the scaled out system will have 16 nodes.
Current system will be scaled out [2x]: =========================================================================== Nodes: Node Count: 2 => 4 --------------------------------------------------------------------------- CPU(Core)/Mem(GB): CPUs/Node: 16 == 16 CPUs Total: 32 => 64 Mem/Node: 65 == 65 Mem Total: 130 => 260 --------------------------------------------------------------------------- AMPs/PEs: AMPs/Node: 24 => 12 AMPs Total: 48 == 48 PEs/Node: 2 == 2 PEs Total: 4 => 8 =========================================================================== 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.