OBProxy O\&M practices

The following error indicates that OBProxy is overloaded by connection requests. In an emergency, you can set the client_max_connections parameter to a larger value to increase the maximum number of allowed connections created through OBProxy between the clients and OceanBase Database. The value range of this parameter is [0, 65535], and its default value is 8192. We recommend that you do not set it too large, because this may cause a memory shortage on the server of OBProxy. The ultimate solution is to scale out the OBProxy service, which is a stateless service.

ERROR 1203 (42000): Too many sessions

The following error indicates a memory shortage. When you see this error, first check if the number of requests is within the normal range. Next, consider increasing the value of the proxy_mem_limited parameter. If you used a command-line tool to install OBProxy without explicitly specifying the memory size, proxy_mem_limited is set to 800 MB by default. You can change it to 2 GB. If you deployed OBProxy by using OceanBase Cloud Platform (OCP), this parameter is set to 2 GB by default during the setting of the startup configuration items.

obproxy's memory is out of limit's 90%

The following error is returned by the accept() function in the Socket library. The error code is 10024, indicating that the system opened too many files. You can use the ulimit -n command of the operating system on which OBProxy is installed to increase the upper limit of open file handles. If the error persists, check if unclosed connections are preventing handles from being released.

failed to accept con(ret=-10024)