Insufficiency or leakage of system memory

In OceanBase Database, the full usage of MemStore memory of business tenants blocks data writes. In addition, if the memory of specific modules, such as the sys500 and sys tenants, is insufficient or leaked, errors occur during data writes or queries. This topic describes how to handle the memory insufficiency or leakage of a system module at the earliest opportunity.

Emergency procedure

In most cases, the memory insufficiency or leakage of a system module in OceanBase Database occurs in a special scenario. For example, a bug exists. To resolve this issue, you can isolate or restart the faulty OBServer node.

Restart the faulty OBServer node

You can resolve the memory exceptions of a system module by restarting the faulty OBServer node. We recommend that you restart the specific OBServer node in the OceanBase Cloud Platform (OCP) console. For more information, see Restart an OBServer node.

Isolate the faulty OBServer node or replica

If the suspected memory insufficiency or leakage of a module cannot be resolved by restarting the faulty OBServer node, you can isolate the OBServer node.

1. Execute the stop server statement. Syntax of the statement:

   ALTER SYSTEM STOP SERVER 'ip:port' [,'ip:port'...] [ZONE='zone']
   

   Example:

   alter system stop server '10.0.0.0.:2882' zone='z1;
   

2. In addition to isolating the faulty OBServer node, you can isolate the entire replica where the exception occurs by executing the stop zone statement. Syntax of the statement:

    ALTER SYSTEM STOP ZONE zoneid;
   

   Example:

   ALTER SYSTEM STOP ZONE z4;