Multi-Node Cliques | Teradata VantageCloud Lake - Increasing Availability with Multi-Node Cliques - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
Language
English (United States)
Last Update
2024-04-03
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

Primary cluster supports multi-node cliques (MNC) on the AWS platform, in addition to the already supported single-node clique (SNC).

High I/O and standard instances are supported for both MNC and SNC, but IOPS SSD (io2 block storage) is required for MNC and SSD (gp3 block storage) is required for SNC.

SNC has a single-node access to a set of storage volumes. If the node goes down, the data stored in those storage volumes become inaccessible.

MNC is a group of nodes sharing access to a set of volumes. If a node goes down, another node in that clique can take over the data stored for the failed node.

Multi-node clique is supported on the AWS platform. Temporarily unavailable on the Azure platform.

When configuring your environment using the VantageCloud Lake Console, these are the defaults:

  • Deployments with 10 or more instances default with provisioned IOPS SSD (io2 Block Express) on the primary cluster.
  • Deployments with count less than 10 instances default with general purpose SSD (gp3) on the primary cluster.

Block storage expansion, scaling up and down on the primary cluster is supported.

Benefits:

  • System availability regardless of infrastructure failure.
  • Faster recovery. From 15-20 minutes to equal or less than 3 minutes approximately.
  • Mitigate impact to system level availability due to storage volume failure by offering higher durable storage to the customer.