15.00 - 15.10 - Hot Standby Nodes - Teradata Database

Teradata Database Introduction to Teradata

Product
Teradata Database
Release Number
15.00
15.10
Content Type
User Guide
Publication ID
B035-1091-151K
Language
English (United States)
Last Update
2018-09-25

Hot standby nodes allow spare nodes to be incorporated into the production environment. Teradata Database can use spare nodes to improve availability and maintain performance levels in the event of a node failure. A hot standby node is a node that:

  • Is a member of a clique.
  • Does not normally participate in Teradata Database operations.
  • Can be brought in to participate in Teradata Database operations to compensate for the loss of a node in the clique.
  • Configuring a hot standby node can eliminate the system-wide performance degradation associated with the loss of a node. A hot standby node is added to each clique in the system. When a node fails, all AMPs and all LAN-attached PEs on the failed node migrate to the node designated as the hot standby. The hot standby node becomes a production node. When the failed node returns to service, it becomes the new hot standby node.

    Configuring hot standby nodes eliminates:

  • Restarts that are required to bring a failed node back into service.
  • Degraded service when vprocs have migrated to other nodes in a clique.