Merge and split resource pools

You can manage resource pools by merging or splitting them.

Merge resource pools

For easier management, you can merge multiple resource pools with the same resource configuration in a tenant into one resource pool.

Limitations

The following limitations apply when merging resource pools:

• The unit_num of the resource pools to be merged must be equal.

• The resource configurations of the resource pools to be merged must be the same.

• The zones that the resource pools to be merged are distributed in must not overlap.

Example procedure

1. Log in to the sys tenant of the cluster as the root user.

2. Execute the following statement to merge resource pools:

   The statement is as follows:

   ALTER RESOURCE POOL MERGE  ('pool_name'[, 'pool_name' ...]) INTO ('merge_pool_name')
   

   Here, pool_name is the name(s) of the resource pool(s) to be merged, and merge_pool_name is the name of the merged resource pool.

   Note

   When you merge resource pools, tenant usage of the resource pools is not affected. The merge only combines multiple resource pools into one from the perspective of Root Service management for easier unified maintenance.

   Example:

   obclient>ALTER RESOURCE POOL MERGE ('pool0','pool1','pool2') INTO ('pool3');
   

Split a resource pool

In daily use, to fully utilize resources, you can split a multi-zone resource pool of a tenant into multiple single-zone resource pools, and then configure different resource configurations for each zone.

Limitations

Only the sys tenant can perform resource pool split operations.

Example background

In daily use, resource pools are usually created as follows:

obclient>CREATE RESOURCE POOL pool1 UNIT='uc0', UNIT_NUM=1, ZONE_LIST=('z1','z2','z3');

The current usage scope of the resource pool pool1 is z1, z2, and z3, and the resource configuration for each zone is uc0. Because the physical server specifications in the three zones (z1, z2, and z3) may differ significantly, using the same resource configuration uc0 in all three zones cannot fully utilize the resources of the physical servers in each zone. Splitting a resource pool can split a multi-zone resource pool into multiple single-zone resource pools, and then you can configure different resource configurations for each single-zone resource pool.

The SQL statement for splitting a resource pool is as follows:

ALTER RESOURCE POOL pool_name SPLIT INTO ('pool_name' [, 'pool_name' ...]) ON ('zone' [, 'zone' ...])

Example procedure

1. Log in to the sys tenant of the cluster as the root user.

2. Split the resource pool pool1 into pool10, pool11, and pool12, and specify new resource unit configurations for the new resource pools.

   obclient>ALTER RESOURCE POOL pool1 SPLIT INTO ('pool10','pool11','pool12') ON ('z1','z2','z3');
   
   ALTER RESOURCE POOL pool10 UNIT='uc1';
   
   ALTER RESOURCE POOL pool11 UNIT='uc2';
   
   ALTER RESOURCE POOL pool12 UNIT='uc3';
   

   After the split, the default resource configurations of the split resource pools remain the same as the original. You can adjust the resource configurations of the new resource pools based on the resource usage in each zone.