High-Latency Escape at the Infrastructure Layer

Availability

This feature is available since openGauss 3.0.0.

Introduction

If the infrastructure layer is abnormal, the database SQL execution latency increases. As a result, the memory or thread pool is overloaded. To deal with this scenario, openGauss provides the automatic escape capability.

Benefits

When the SQL execution latency increases, sessions are stacked, and the memory or thread pool is overloaded, the database cannot provide services due to exceptions at the infrastructure layer. In this scenario, escape is possible to recover the database so as to provide services within a short period of time.

Description

• When the database memory is overloaded, sessions are killed instantly and new connections are forbidden till the memory is recovered to provide services. The memory threshold is specified by the resilience_memory_reject_percent GUC parameter. By default, this function is disabled.
• When the number of stacked sessions in the database reaches the upper limit of the thread pool, sessions are killed instantly and new connections are forbidden till the number of sessions decreases to the acceptable range of the thread pool. Then, services are recovered. The session threshold is specified by the resilience_thread_reject_cond GUC parameter. By default, this function is disabled.

Enhancements

None

Constraints

• When the escape capability is triggered due to memory or thread pool overload, the sessions of users with the sysadmin or monitoradmin permission are not cleared.
• In upgrade mode, this feature is not triggered.

Dependencies

None