ODP failure

Failures related to OceanBase Database Proxy (ODP), also called OBProxy, mainly fall into two categories: one is the failure of the ODP node itself, and the other is the failure of the load balancing components (usually F5, LVS, SLB, etc.) at the upper layer of a cluster composed of multiple ODP nodes. This topic provides information on how to handle the failure of the ODP node itself in emergency situations.

Emergency handling procedure

Failures caused by ODP itself generally fall into the following situations:

• The ODP process frequently exits due to the out-of-memory (OOM) error.

  If the ODP process exits due to insufficient memory, you can find the following error message in the obproxy log: obproxy's memory is out of limit's 90%. The proxy_mem_limited parameter in ODP is used to modify the memory limit of OBProxy. This parameter specifies the maximum upper limit of system memory that the proxy can occupy; the process actively exits when this limit is exceeded. The value range is [100MB, 100GB]. The modification takes effect immediately without a restart.

  • If the ODP is deployed through OCP, the default startup configuration already sets this parameter to 2 GB. In this scenario, the parameter value can be increased to 8 GB.

  • If the ODP is deployed through the command line without explicitly specifying the memory size, the default value for proxy_mem_limited is 800 MB. In this scenario, you can try increasing the parameter value to 2 GB as follow:

    ALTER proxyconfig SET proxy_mem_limited = 2G;
    

• The ODP cannot automatically restart due to the abnormal daemon process.

  In this scenario, you can manually restart the ODP.