Health Condition Duration | Teradata Vantage - Health Condition Duration - Advanced SQL Engine - Teradata Workload Management

Teradata Vantageā„¢ - Workload Management User Guide

Product
Advanced SQL Engine
Teradata Workload Management
Release Number
17.10
Published
July 2021
Language
English (United States)
Last Update
2021-07-28
dita:mapPath
pzr1600284001549.ditamap
dita:ditavalPath
pzr1600284001549.ditaval
dita:id
B035-1197
lifecycle
previous
Product Category
Software
Teradata Vantage

When you define a health condition, you can associate it with a minimum qualifying duration. To understand why, consider the following scenario. The system has a RED health condition for degraded health and a GREEN health condition for good health. When an event causes the RED health condition, the state associated with RED goes into effect. RED may have lower throttles limits, more filters, and a lower workload share percent. If, after it transitions to RED, the system immediately returns to good health, the system could transition to the GREEN health condition and the more restrictive values could be lifted.

To prevent continual state transitions, set a minimum qualifying duration for health conditions. This gives the system a better chance of resolving the issues that are causing the degraded state. Teradata recommends that health conditions that are caused by internal events (not user-defined events) be set to a minimum duration of 10 minutes (600 seconds).