Drop unit configs

2024-04-19 08:42:50  Updated

This topic describes how to drop unit configs.

Prerequisites

Before dropping a unit config, you must ensure that it is not in use. If it is being used by a tenant, remove it from the resource pool of the tenant first. For detailed instructions, see Modify attributes of a resource pool.

Procedure

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

    obclient -h172.30.xx.xx -P2883 -uroot@sys#cluster -p**** -A
    
  2. Access the database named oceanbase.

    obclient [(none)]> USE oceanbase;
    
  3. Confirm the usage information of the unit config through the DBA_OB_UNIT_CONFIGS and DBA_OB_RESOURCE_POOLS views.

    If the UNIT_NAME column in the query result does not contain the name of the target unit config, the unit config is not allocated to a resource pool. If the UNIT_NAME column in the query result contains the name of the target unit config, the unit config is allocated to a resource pool.

    As you can see from the example below, the unit config named S2_unit_config is not allocated to a resource pool.

    obclient [oceanbase]> SELECT a.UNIT_CONFIG_ID, a.NAME AS UNIT_NAME, b.NAME AS POOL_NAME FROM oceanbase.DBA_OB_UNIT_CONFIGS a,oceanbase.DBA_OB_RESOURCE_POOLS b WHERE b.UNIT_CONFIG_ID=a.UNIT_CONFIG_ID;
    +----------------+-------------------------------+--------------------------+
    | UNIT_CONFIG_ID | UNIT_NAME                     | POOL_NAME                |
    +----------------+-------------------------------+--------------------------+
    |              1 | sys_unit_config               | sys_pool                 |
    |           1001 | config_mysql001_zone1_S1_okz  | pool_mysql001_zone1_okz  |
    |           1002 | config_mysql001_zone2_S1_pme  | pool_mysql001_zone2_pme  |
    |           1003 | config_mysql001_zone3_S1_jsu  | pool_mysql001_zone3_jsu  |
    |           1013 | config_oracle001_zone3_S1_exu | pool_oracle001_zone3_exu |
    |           1014 | config_oracle001_zone2_S1_hli | pool_oracle001_zone2_hli |
    |           1015 | config_oracle001_zone1_S1_owy | pool_oracle001_zone1_owy |
    |           1020 | S1_unit_config                | mq_pool_01               |
    +----------------+-------------------------------+--------------------------+
    8 rows in set
    

    For more information about the DBA_OB_UNIT_CONFIGS view, see DBA_OB_UNIT_CONFIGS.

    For more information about the DBA_OB_RESOURCE_POOLS view, see DBA_OB_RESOURCE_POOLS.

  4. Execute the DROP RESOURCE UNIT statement to drop the unit config.

    An example of dropping a unit config named S2_unit_config is as follows:

    obclient [oceanbase]> DROP RESOURCE UNIT S2_unit_config;
    Query OK, 0 rows affected
    

    For more information about the DROP RESOURCE UNIT statement, see DROP RESOURCE UNIT.

  5. Query the DBA_OB_UNIT_CONFIGS view to confirm that the unit config has been successfully dropped.

    obclient [oceanbase]> SELECT * FROM DBA_OB_UNIT_CONFIGS WHERE NAME = 'S2_unit_config';
    Empty set
    

References

Contact Us