High availability needs to be configured for OceanBase Database Proxy (ODP) to ensure service continuity. User requests first arrive at ODP. If ODP fails, the requests cannot be properly handled. ODP also copes with OBServer node failures and performs fault tolerance operations.
Unlike OceanBase clusters, ODP has no persistent data, and needs to access OceanBase Database to obtain the required data. Therefore, ODP failures do not cause data loss. Multiple ODP instances form a cluster to provide services. A specific ODP instance for handling requests is determined by an F5 load balancer or another load balancer. If an ODP instance fails, the load balancer automatically removes the instance to ensure that new requests are not forwarded to it.
ODP monitors the cluster status in real time in the following ways: ODP obtains the cluster system table in real time to check the health status of each OBServer node and the real-time location of each partition. ODP also monitors the service status of OBServer nodes based on network connections. When ODP detects exceptions, it marks the corresponding OBServer nodes as failed and switches the services to functioning OBServer nodes.
References
For more information about ODP, see Overview.