When multiple users or services use the same Lindorm cluster, resource preemption always occurs. The reads and writes of some important online services may be adversely affected by multiple concurrent reads and writes of offline services. ApsaraDB for Lindorm provides the group feature to isolate resources between multiple tenants. To isolate the resources, you can assign RegionServers to different groups and host different tables in the group.

The preceding figure shows that RegionServer1 and RegionServer2 are assigned to Group1 and RegionServer3 and RegionServer4 are assigned to Group2. Table1 and Table2 are also moved to Group1. In this case, all regions of Table1 and Table2 are distributed to RegionServer1 and RegionServer2 in Group1. All regions of Table3 and Table4 are distributed to RegionServer3 and RegionServer4 in Group2. Therefore, the requests to Table1 and Table2 are sent to LDServer1 and LDServer2. The requests to Table3 and Table4 are sent to LDServer3 and LDServer4. This allows you to isolate resources.

View group information

You can view the information of all groups of the current cluster on the homepage. If you have not created a group, the system provides a default group. All RegionServers and tables belong to the default group.group

Create a group

On the Groups page, choose More > Create Group. After a new group is created, the numbers of servers and tables in this group are both 0. You must move servers and tables to this group.create groupgroupname

Delete a group

On the homepage of ClusterManager, click Delete next to the required group to delete the group. Note: Before you delete a group, you must delete all tables and servers in the group. Otherwise, the delete operation fails.

Move a RegionServer to a group

By default, all RegionServers belong to the default group. You must move the servers to the required group before you use them. To move a RegionServer to a group, perform the following steps:
  1. On the homepage of ClusterManager, select the required RegionServer in the Cluster servers table and click Move.movegroup
  2. In the dialog box that appears, select the required group from the drop-down list and click OK.newGoup
Note
  • If you move a table to a group that does not contain a RegionServer, the region of the table cannot be accessed because no online server is available.
  • We recommend that you distribute at least two RegionServers to a group. If one of the RegionServers no longer responds, you can access another server in the same group. If the only RegionServer in a group no longer responds, all tables in this group cannot be accessed.
  • After you move a RegionServer to a group, the online regions on this RegionServer are shared among all other RegionServers in the group and requests are evenly distributed to these regions. This ensures load balancing.

Configure the group for a namespace

If you do not configure a group for a namespace, all tables that you create belong to the default group. Regions are only available in the default group. If you do not want to group tables every time you create tables, you can specify a group for the namespace. All tables created in this namespace can be added to the same group.
  1. On the Namespaces page of ClusterManager, click Bind Group next to the required namespace.bindgroup
  2. In the dialog box that appears, select the target group from the drop-down list and click OK.bindgroupnewgroup
Note
  • If you modify the group information of the namespace, the groups of the existing tables in this namespace are not changed.
  • If you have bound a group to the namespace, all tables created in this namespace also belong to this group. You can move the tables to other groups.

Move a table to a group

To move a table to the required table, perform the following steps:
  1. On the User tables page of ClusterManager, select the required table and click Move next to the table.movetable
  2. In the dialog box that appears, select the target group from the drop-down list and click OK.movegroup1
Note You must move tables to the group that contains RegionServers. Otherwise, these tables cannot be found in existing regions.