This topic describes how to manage the endpoints of Orca in a PolarDB for MySQL cluster.
Default and custom endpoints
Endpoint type | Description | Scenario |
Default endpoint | If you specify to enable Orca when you create a PolarDB for MySQL cluster, a default Orca endpoint is assigned to the cluster. The default Orca endpoint service is provided by PolarProxy. The default Orca endpoint supports automatic read/write splitting. Write requests to the Orca endpoint are routed to the primary node and read requests to the endpoint are routed to read-only nodes. For information about PolarProxy, see PolarProxy. | You can use the default endpoint for business that requires read/write splitting. If you use the default endpoint, you can add read-only nodes to the cluster to enable fast, real-time business expansion. |
Custom endpoint | PolarDB for MySQL allows you to create custom Orca endpoints. The services of the Orca endpoints are provided by PolarProxy.
|
|
In-Memory Column Index (IMCI) nodes do not support the Orca feature. Requests to the Orca endpoints cannot be routed to IMCI nodes.
Create an Orca custom endpoint
Log on to the PolarDB console.
In the left-side navigation pane, click Clusters.
In the upper-left corner, select the region in which the cluster is deployed.
Find the cluster and click its ID.
In the Database Connections section of the Basic Information page, click Create Custom Cluster Endpoint. Set the Endpoint Type parameter to Orca Endpoint, configure the Endpoint Name parameter, and then configure PolarProxy. For more information, see Configure PolarProxy.
NoteSet the Endpoint Type parameter to Orca Endpoint.
For an Orca endpoint, you can only configure the load balancing policy and specify whether the primary node accepts read requests for load balancing, and configure the consistency level for the consistency settings. You cannot configure the connection pool, hybrid transactional and analytical processing (HTAP) optimization, or security protection settings.
Modify an Orca endpoint
Log on to the PolarDB console.
In the left-side navigation pane, click Clusters.
In the upper-left corner, select the region in which the cluster is deployed.
Find the cluster and click its ID.
In the Database Connection section of the Basic Information page, find the endpoint that you want to manage and click
> Edit to the right of Private or Public endpoint to modify the endpoint.
The prefix of the endpoint must meet the following requirements:
It must be 6 to 40 characters in length and can contain lowercase letters, digits, and hyphens (-).
It must start with a lowercase letter and end with a digit or letter.
The port number must be within the range of 3000 to 5999.
If SSL is enabled for the endpoint, the cluster restarts after you modify the endpoint.
If SSL is enabled for the endpoint, the total length of the new endpoint cannot exceed 64 characters.
Release an Orca endpoint
Before you release an endpoint, make sure that your application is using a new endpoint to access the database.
After you release an endpoint, you cannot restore the endpoint. You can only recreate the endpoint.
Log on to the PolarDB console.
In the left-side navigation pane, click Clusters.
In the upper-left corner, select the region in which the cluster is deployed.
Find the cluster and click its ID.
In the Database Connection section of the Basic Information page, find the endpoint you want to release and click Release in the upper-right corner to release the endpoint.
In the dialog box that appears, click OK.