EMR Serverless StarRocks offers a multi-gateway feature to ensure the isolation and stability of Frontend (FE) services. In compute-storage separated scenarios, you can assign independent gateways for different business needs. When an instance experiences a high load, you can route critical queries through a specific gateway to dedicated FE nodes. This maintains service performance and reliability.
Prerequisites
You have created a compute-storage separated instance. For more information, see Create an instance.
Limits
This feature is available only for instances with a minor version of 1.7.9 or later, such as 3.3.8-1.94-1.7.10.
View the default gateway
The system automatically creates a default gateway to handle all query requests that do not specify a gateway. Follow these steps to view the default gateway information.
-
Go to the instance details page of EMR Serverless StarRocks.
-
Log on to the E-MapReduce console.
-
In the navigation pane on the left, choose .
-
In the top menu bar, select a region as needed.
-
Click the name of the target instance.
-
-
On the Instance Details page, view the default gateway information in the Gateway Information section.
Parameter
Description
Internal Endpoint
The private endpoint of the gateway. Applications or services within the same VPC can use this endpoint.
-
View Private Zones: View the DNS record.
-
Activate SLB: After you enable SLB, a Server Load Balancer (SLB) instance (small I, slb.s1.small) is used for load balancing.
Important-
Enabling SLB incurs charges. For more information, see CLB Billing Overview.
-
After you switch to SLB, you cannot switch back to PrivateZone.
After you enable SLB, click View SLB. You will be redirected to the Alibaba Cloud Server Load Balancer (SLB) console to view details of the associated SLB instance.
-
Public Endpoint
Access and use the StarRocks instance over the public network. The instance remains accessible from within the Alibaba Cloud VPC after you enable public access.
To access the gateway from the public network, click Enable Access over Internet.
ImportantEnabling public access creates a CLB instance and incurs charges. For more information, see CLB Billing Overview.
Enable leader write only
Specifies whether to restrict the leader node to handle only write requests, such as data import operations, instead of query requests.
-
Disabled: The leader node handles both write and query requests.
-
Enabled: The leader node handles only write requests. Other follower nodes handle query requests.
In high-concurrency write scenarios, enable this option to reduce the load on the leader node and improve write performance.
Network Type
The network connection type used by the current gateway.
Number of Associated FEs
The number of FE nodes associated with the current gateway.
The default gateway automatically associates with the initial FE nodes at initialization and with new FE nodes after a scale-out. If no new gateways are created, the default gateway remains associated with all available FE nodes.
-
Create a gateway
The default gateway is suitable for most scenarios. If your business requires greater isolation or performance optimization, you can create a custom gateway.
-
Creating a new gateway might briefly interrupt some queries. Perform this operation during off-peak hours to minimize the impact on your business.
-
Creating a new gateway incurs SLB charges. For more information, see SLB Billing Overview.
-
You cannot create a gateway if there are not enough FE nodes. In this case, you must first scale out the FE nodes. For more information about scaling, see Scale instances.
-
Enable SLB.
-
On the Instance Details page, in the Gateway Information section, click Activate SLB.
-
In the dialog box that appears, click OK.
-
-
On the Instance Details page, in the Gateway Information section, click Create Gateway.
-
In the Create Gateway dialog box, configure the following parameters.
Parameter
Description
Gateway Name
Enter a name for the gateway for easy identification and management.
Number of Nodes to Allocate
When you create a new gateway, you can flexibly assign FE nodes to it as needed. Nodes are assigned in a step size of 2.
For example, your default gateway is associated with 3 FE nodes. After you scale out by adding 2 more nodes, the default gateway has 5 FE nodes. When you create a new gateway, you can assign 2 of these nodes to the new gateway. This lets you manage the added resources independently.
-
Click OK.
Modify a gateway
-
On the Instance Details page, in the Gateway Information section, click Modify Gateway to the right of the gateway you created.
-
In the dialog box, modify the Gateway Name and Number of Nodes to Allocate parameters. Then, click OK.
Delete a gateway
-
You can delete only the gateways that you created.
-
Before you delete a gateway, make sure no services are connected to it. After the gateway is deleted, all tasks submitted by clients that were connected to it will fail.
-
On the Instance Details page, in the Gateway Information section, click Delete Gateway to the right of the gateway you created.
-
In the dialog box that appears, click OK.