The number of obproxy threads is 8,192 by default. If the number of connections requested by applications exceeds this value, the excess connections will be denied. This topic provides information on how to handle obproxy thread exhaustion in emergency situations.
Emergency handling procedure
obproxy thread exhaustion generally does not occur. If you encounter this issue, you can address it based on the following two scenarios:
obproxy nodes being centrally deployed in a cluster
If you are using a centrally deployed obproxy cluster and you are facing obproxy thread exhaustion, it is recommended to expand this cluster by adding new obproxy nodes through OCP. New obproxy nodes can share the application connection requests. You can add obproxy nodes to the cluster through OCP by following the steps below:
Log on to the OCP console.
In the left-side navigation pane, click OBProxy.
In the cluster list, select the OBProxy cluster that you want to manage to go to the overview page of the OBProxy cluster.
Click Add OBProxy.
In the dialog box that appears, specify the information such as Software Version, IDC, SQL Port, Exporter, Server Type, Server Selection Method, and Host.
Click OK.
For more information, see Add an ODP.
Single-node deployment of obproxy or an unscalable obproxy cluster
If you are using a single-node deployment of obproxy or using an unscalable obproxy cluster, you can consider temporarily increasing the maximum allowable connection threads. Modify the obproxy cluster configuration parameter directly in the OCP console by referring to OCP User Guide.