DWHPro Insights

Hot Standby Nodes: The Secret to Seamless Performance and Recovery

By Roland Wenzlofsky ·

Hot Standby Nodes: The Secret to Seamless Performance and Recovery

A hot standby node belongs to a clique of nodes and does not host virtual processes such as AMPs or Parsing Engines.

The standby node remains idle until a member of its clique crashes or fails. At this point, the standby node is activated to take over the failed node’s responsibilities.

Failover may move AMPs to a standby node, but interruption and performance effects depend on platform, state recovery and workload. No failover or negligible-loss guarantee was tested.

HSN1
Node crashes, migration of AMPs takes place

The intelligence of the design lies in the fact that once the failed node goes back online, it automatically takes over as the active standby node.

HSN2
The recovered node becomes the new HSN

This describes a platform-specific clique/hot-standby architecture, not every cloud or Teradata deployment. Confirm recovery and availability behavior for the actual system.

Need help with query performance or platform costs?

Diagnose plans, skew, spool pressure and expensive workloads. Agree a baseline and acceptance criteria before making changes.

Explore Teradata performance tuning

Practical data engineering insights, regularly

Join more than 3,500 data professionals: a regular newsletter with practical insights on data engineering, new data platforms (Snowflake, Databricks, Teradata) and AI.

Follow DWHPro in Google to see our articles more often in Search.

Leave a Comment

Get more practical data engineering advice

Join the DWHPro newsletter for practical data engineering tips, troubleshooting examples and data platform insights.

Protected by Security by CleanTalk and CleanTalk Anti-Spam