Change resources of services and components|V4.3.2| docs|Distributed Database

OceanBase Admin Toolkit (OAT) allows you to modify the configurations of node resources for services and components that are in use. For example, you can add, remove, or replace nodes based on resource environment changes.

Overview

Resource change type	Description
Add a node	You can add nodes to improve service performance or availability.
Remove a node	You can remove existing nodes to reduce resource usage of services.
Replace a node	You can replace damaged nodes or those no longer in use to improve service stability.

You can make changes to the following products, components, and tools:

Products: OCP, ODC, OMS, and OB Sharding
Components: MetaDB, OBDNS, NLB, and SQLAuditStore
Tools: OBLB

Procedure

To change the resources of a service or component, perform the following steps:

In the left-side navigation pane, choose Product Service > Products or Product Service > Components.
On the Products or Components page, find the service or component whose resources you want to change and click its name to go to the details page.
On the details page, click Resource Change.
After you change the resources, click OK. You can also click Cancel to cancel the changes.

Change OCP resources

You can change the resources of OCP in multi-zone mode or non-multi-zone mode.

Multi-zone mode

The following table describes the parameters for changing the resources of OCP in multi-zone mode.

Parameter	Description
Multi-zone Mode	Specifies whether to enable the multi-zone mode. If OCP is in multi-zone mode, this parameter is enabled by default and cannot be disabled. If multi-zone mode is enabled for OCP, remain at least one zone when you remove zones.
Server	The server for deploying the resources of OCP. You can add and remove servers.
Add Zone	The zone for deploying the resources of OCP. You can add zones if OCP is in multi-zone mode. In this case, you must specify the name, server, OCP proxy, and MetaDB proxy for each zone.
CPU & Memory	The number of CPU cores and memory size configured for OCP. You can modify the configurations. Note If you reduce the number of CPU cores or memory size when OCP is running, the performance of OCP can be affected. Proceed with caution.

Non-multi-zone mode

The following table describes the parameters for changing the resources of OCP in non-multi-zone mode.

Parameter	Description
Server	The server for deploying the resources of OCP. You can add and remove servers.
CPU & Memory	The number of CPU cores and memory size configured for OCP. You can modify the configurations. Note If you reduce the number of CPU cores or memory size when OCP is running, the performance of OCP can be affected. Proceed with caution.

Change ODC resources

The following table describes the parameters for changing the resources of ODC.

Parameter	Description
Server	The server for deploying the resources of ODC. You can add and remove servers.
CPU & Memory	The number of CPU cores and memory size configured for ODC. You can modify the configurations. Note If you reduce the number of CPU cores or memory size when ODC is running, the performance of ODC can be affected. Proceed with caution.

Change OMS resources

The following table describes the parameters for changing the resources of OMS.

Parameter	Description
Server	The server for deploying the resources of OMS. You can add servers.
CPU & Memory	The number of CPU cores and memory size configured for OMS. You can modify the configurations. Note If you reduce the number of CPU cores or memory size when OMS is running, the performance of OMS can be affected. Proceed with caution.

Change MetaDB resources

The following table describes the parameters for changing the resources of MetaDB.

Parameter	Description
Server	The server for deploying the resources of MetaDB. You can add, replace, and remove servers.
CPU & Memory	The number of CPU cores and memory size configured for MetaDB. You can modify the configurations. Note If you reduce the number of CPU cores or memory size when MetaDB is running, the performance of MetaDB can be affected. Proceed with caution.

Note

After you click OK, OAT displays a message indicating that the resource changes of MetaDB take effect only after you restart the cluster and all services associated with MetaDB are unavailable during the restart.

Change OBDNS resources

The following table describes the parameters for changing the resources of OBDNS.

Parameter	Description
Server	The server for deploying the resources of OBDNS. You can add and replace servers. Note Single-node OBDNS does not support replacement operations. One task can change only one OBDNS node.
CPU & Memory	The number of CPU cores and memory size configured for OBDNS. You can modify the configurations. Note If you reduce the number of CPU cores or memory size when OBDNS is running, the performance of OBDNS can be affected. Proceed with caution.
Synchronize changes to OCP	Optional. Whether to synchronize changes to OCP for management.

Change OB Sharding resources

The following table describes the parameters for changing the resources of the odpconsole.

Parameter	Description
Server	The server for deploying resources of the OB Sharding console. You can add, replace, and remove servers.
CPU & Memory	The number of CPU cores and memory size configured for the odpconsole. You can modify the configurations. Note If you reduce the number of CPU cores or memory size when the odpconsole is running, the performance of the odpconsole can be affected. Proceed with caution.

The following table describes the parameters for changing the resources of the odpserver.

Note

You can add, remove, or replace nodes for the odpserver or modify the resource configurations of existing nodes.

Parameter	Description
Server	The server for deploying resources of the odpserver. You can add, replace, and remove servers.
Port	The port number.
CPU & Memory	The number of CPU cores and memory size configured for the odpserver. You can modify the configurations. Note If you reduce the number of CPU cores or memory size when the odpserver is running, the performance of the odpserver can be affected. Proceed with caution.
CPUSET-CPUS	Optional. The CPU cores to be used.

Change NLB resources

Note

You can add nodes, replace nodes, and modify the resource specifications of existing nodes for NLB. Take note that NLB in single-node mode does not support node replacement.

The following table describes the parameters for changing the resources of NLB.

Parameter	Description
Server	The server for deploying resources of NLB. You can add and replace servers.
CPU & Memory	The number of CPU cores and memory size configured for NLB. You can modify the configurations. Note If you reduce the number of CPU cores or memory size when NLB is running, the performance of NLB can be affected. Proceed with caution.

Change SQLAuditStore resources

The following table describes the parameters for changing the resources of SQLAuditStore.

Parameter	Description
CPU & Memory	The number of CPU cores and memory size configured for SQLAuditStore. You can modify the configurations. Note If you reduce the number of CPU cores or memory size when SQLAuditStore is running, the performance of SQLAuditStore can be affected. Proceed with caution.

Change OBLB resources

The following table describes the parameters for changing the resources of OBLB.

Parameter	Description
Server	The server for deploying resources of OBLB. You can add and replace servers. Note Single-node OBLB does not support replacement operations. One task can change only one OBLB node.
Synchronize changes to OCP	Optional. Whether to synchronize changes to OCP for management.