When Multiple Nodes Fail | Teradata Vantage on AWS (DIY) - When Multiple Nodes Fail - Teradata Vantage on AWS

Teradata Vantageā„¢ on AWS (DIY) Installation and Administration Guide

Product
Teradata Vantage on AWS
Release Number
2.3
Published
April 2022
Language
English (United States)
Last Update
2022-04-18
dita:mapPath
zra1648797736961.ditamap
dita:ditavalPath
nat1649317391363.ditaval
dita:id
B035-2800
lifecycle
previous
Product Category
Cloud

When two or more nodes fail at the same time, all nodes can be replaced at the same time as long as one node remains running to act as the node failure recovery control node. However, if both BYNET relay nodes in the database are unavailable during node failure recovery, the database stops. If one or more replacement instances cannot be spun up, the database is brought back up running on Fallback and logons are enabled. If there are two nodes in the same fallback cluster for the AMPs associated with these two nodes, logons are enabled, but queries fail because they reference data from the same fallback cluster where both AMPs are inaccessible. Queries that do not reference data from the failed fallback clusters still work.

If two or more nodes fail at different times while node failure recovery is in progress, contact Teradata Customer Support.