The grouping feature in Lindorm achieves multi-tenant isolation by assigning RegionServers to different groups and storing specific tables in each group, ensuring resource isolation across workloads.
Background
When multiple users or services share a single Lindorm cluster, critical online read and write operations can be affected by offline batch processing tasks. The group feature addresses this by isolating resources. For example, you can create Group1 with RegionServer1 and RegionServer2, and Group2 with RegionServer3 and RegionServer4. After you move Table1 and Table2 to Group1, all their Regions are scheduled exclusively on RegionServer1 and RegionServer2. Similarly, Regions for Table3 and Table4 run exclusively on RegionServer3 and RegionServer4. This ensures that workloads in different groups do not compete for the same server resources.
Prerequisites
You are logged on to the cluster management system for the target instance. For more information, see Log on to the cluster management system.
View groups
-
In the left-side navigation pane of the cluster management system, choose .
-
At the bottom of the page, you can view information about all groups in the cluster.
NoteIf you have not created any groups, the system creates a default group named default. All RegionServers and tables belong to this group.
On the Group and Node Overview page, filter results by IDC, Group, or Node from the filter bar and click Query. The table displays node metrics such as Read requests/s, Write requests/s, Replicated write traffic/s, Total Shards, Read data (KB/s), Average read RT (ms), Write data (KB/s), and Average write RT, along with the Group each node belongs to. In the Actions column, click More to view additional details.
Create a group
-
In the left-side navigation pane of the cluster management system, choose .
-
In the upper-right corner of the page, click +Add.
-
In the Create Group dialog box, enter a Group Name.
-
Click Determine.
NoteA newly created group is empty. You must then move the required servers and tables into it.
Delete a group
To delete a group, you must first move all servers and tables out of it.
-
In the left-side navigation pane of the cluster management system, choose .
-
In the Operation column for the target group, choose .
-
In the dialog box, click Determine.
View basic instance/cluster information
-
In the left-side navigation pane of the cluster management system, choose .
-
In the Basic Instance/Cluster Information section, you can view information such as the database type and the IDC where the database is deployed.
-
On the right, click to adjust the read/write permissions for the current instance or cluster.
Move a RegionServer
-
By default, all RegionServers belong to the default group. To use groups, you must move RegionServers to the intended groups.
-
If you move a table to a group that has no RegionServers, the table's Regions will fail to come online because no servers are available. As a result, the table becomes inaccessible.
-
We recommend that you assign at least two RegionServers to each group. If one RegionServer becomes unavailable, the table's Regions can be reassigned to another RegionServer in the same group. If a group has only one RegionServer and it becomes unavailable, all tables in that group become inaccessible.
-
When you move a RegionServer to a different group, the Regions that it serves are immediately reassigned to other RegionServers in its original group.
-
In the left-side navigation pane of the cluster management system, choose .
-
Find the target node. In its Actions column, choose .
-
In the Move Group dialog box, select a Destination Group.
-
Click Determine.
Move a table
Do not move a table to a group that has no servers. Otherwise, the table will become inaccessible.
-
On the Overview page, click Move Group in the Operation column. In the HBase table management list, find the target table (such as test1), and click Move Group in its Actions column.
-
In the Move Group dialog box, select a Destination Group.
-
Click Determine.