OceanBase
English日本語简体中文
Docs Home
Products
Integrations
Release Notes

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service
OceanBase DatabaseOceanBase Cloud ToolsConnectors and MiddlewareLifecycle Support Policy

OceanBase Deployer

V4.3.0Community Edition
  • What is obd
  • Quick Start
    • Install obd
    • Quick deployment of OceanBase Database
    • Quickly deploy OCP
  • obd Command
    • Quick deployment commands
    • Cluster commands
    • Command groups
    • Image and repository commands
    • Test command groups
    • Tool commands
    • obdiag commands
    • Binlog service commands
    • Hardware commands
    • License commands
    • Password commands
    • Telemetry commands
  • User Guide
    • Usage overview
    • Deploy through GUI
      • Overview
      • Pattern configuration rules
      • Deploy an OceanBase cluster
      • Deploy OCP
      • Deploy OMS
      • Change components
      • Upgrade OCP
      • Upgrade OMS
    • Deploy through CLI
      • Configuration file
      • Component deployment
        • Deploy an OceanBase cluster
        • Deploy seekdb
        • Deploy obconfigserver
        • Deploy OMS
        • Deploy OCP
        • Deploy Alertmanager
        • Deploy obbinlog
        • Deploy oblogproxy
      • Cluster management
        • Physical Standby Database
          • Create a standby tenant
          • Role switching and decoupling
          • Switch the synchronization mode between primary and standby tenants
        • seekdb primary/standby instance
          • Create a standby instance
          • Role switching and decoupling
        • Scale out and component changes
        • Performance test
        • Diagnose a cluster
        • Backup and restore
        • Add a GUI monitoring system to an existing cluster
      • Cluster management
        • Use OCP to take over an OceanBase cluster deployed by obd
        • Take over an OceanBase cluster
      • Component upgrade
        • Upgrade OceanBase Database
        • Upgrade ODP
        • Upgrade OMS
  • Upgrade obd
  • FAQ
  • Error codes
  • Release Notes
    • Version rules
    • V4.3
      • OceanBase Deploy V4.3.0
    • V4.2
      • OceanBase Deployment Tool V4.2.0
    • V4.1
      • OceanBase Deployer V4.1.0
    • V4.0
      • OceanBase Deployer V4.0.0
    • V3.6
      • OceanBase Deployer V3.6.0
    • V3.5
      • OceanBase Deployer V3.5.0
    • V3.4
      • OceanBase Deployer V3.4.0
    • V3.3
      • OceanBase Deployer V3.3.0
    • V3.2
      • OceanBase Deployer V3.2.2
      • OceanBase Deployer V3.2.1
      • OceanBase Deployer V3.2.0
    • V3.1
      • OceanBase Deployer V3.1.2
      • OceanBase Deployer V3.1.1
      • OceanBase Deployer V3.1.0
    • V3.0
      • OceanBase Deployer V3.0.1
      • OceanBase Deployer V3.0.0
    • V2.10
      • OceanBase Deployer V2.10.1
      • OceanBase Deployer V2.10.0
    • V2.9
      • OceanBase Deployer V2.9.2
      • OceanBase Deployer V2.9.1
      • OceanBase Deployer V2.9.0
    • V2.8
      • OceanBase Deployment Tool V2.8.0
    • V2.7
      • OceanBase Deployment Tool V2.7.0
    • V2.6
      • OceanBase Deployment Tool V2.6.2
      • OceanBase Deployment Tool V2.6.1
      • OceanBase Deployment Tool V2.6.0
    • V2.5
      • OceanBase Deployer V2.5.0
    • V2.4
      • OceanBase Deployer V2.4.0
    • V2.3
      • OceanBase Deployment Tool V2.3.1
      • OceanBase Deployer V2.3.0
    • V2.2
      • OceanBase Deployment Tool V2.2.0
    • V2.1
      • OceanBase Deployer V2.1.1
      • OceanBase Deployment Tool V2.1.0
    • V2.0
      • OceanBase Deployment Tool V2.0.1
      • OceanBase Deployment Tool V2.0.0
    • V1.6
      • OceanBase Deployer V1.6.2
      • OceanBase Deployer V1.6.1
      • OceanBase Deployer V1.6.0
    • V1.5
      • OceanBase Deployer V1.5.0
    • V1.4
      • OceanBase Deployer V1.4.0
    • V1.3
      • OceanBase Deployer V1.3.3
      • OceanBase Deployer V1.3.2
      • OceanBase Deployer V1.3.0
    • V1.2
      • OceanBase Deployer V1.2.1
      • OceanBase Deployer V1.2.0
  • Interactive deployment of OceanBase Database Community Edition
  • Deploy a Community Edition cluster using the obd graphical interface
  • Deploy a Community Edition cluster by using an obd configuration file

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Deployer
  3. V4.3.0

Change components

Last Updated:2026-09-04 08:21:29

Prerequisites
Install the component
Step 1: Start the graphical interface
Step 2: Deployment configuration
Step 3: Component configuration
Step 4: Precheck
Step 5: Deploy
Uninstall a component
Step 1: Start the graphical interface
Step 2: Uninstall the component
Step 3: Uninstall

This topic describes how to add or delete components in the graphical interface.

Prerequisites

Before you start, make sure that you have met the following conditions:

  • You have installed obd V2.10.0 or later. We recommend that you install the latest version. For more information, see Install obd.

  • obd manages at least one running OceanBase cluster.

  • You can log in to the node where the component to be added is located by using password-free SSH.

Install the component

Step 1: Start the graphical interface

  1. Start the graphical interface

    Run the obd web command in the command line to start the graphical interface, and click the provided address to access it.

    [admin@test001 ~]$ obd web
    start OBD WEB in 0.0.0.0:8680
    please open http://10.10.10.1:8680
    

    Note

    • The graphical interface by default uses port 8680. You can use the obd web -p <PORT> command to specify the port, which must be in the range [1025, 65535].

    • In Alibaba Cloud or other cloud environments, the program may fail to obtain a public IP address and instead output an internal IP address. This IP address is not a public IP address, so you need to use the correct IP address to access the graphical interface.

    • The obd web command is bound to 0.0.0.0. In a multi-network card deployment, you can access the graphical interface using any accessible IP address.

    • You can use the nohup or screen command to run the obd web command in the background.

  2. (Optional) Place the cursor on the Chinese character in the upper-right corner of the graphical interface and click to switch between Chinese and English interfaces based on the displayed language.

  3. Click Start Your Trial on the interface, and in the Welcome to the OceanBase Deployment Wizard window, select the Component Management module. Place the cursor on the Manage button and select the corresponding component management method. In this case, select Component Installation.

Step 2: Deployment configuration

You can select the components to be installed on the Deployment Configuration page. The Deployment Configuration page contains the following information.

Module
Description
Deployment Object Select the cluster to add the component. Click the dropdown list below Cluster to display all running clusters managed by obd. Click the name of the corresponding cluster to add the component to it.
Select Deployment Components After you select a cluster, this section displays the components deployed in the cluster and the components that can be added. Click the checkbox before the corresponding component to select whether to install it. The component version is fixed to the latest version. Click Learn More after the corresponding component to view its documentation.

After you select the deployment components, click Next in the lower-right corner to go to the Component Configuration page.

Step 3: Component configuration

You can configure the nodes, ports, and other related settings for the components to be deployed on the Component Configuration page. The component deployment page contains the following information.

Module
Description
Component Node Configuration You can configure the IP address of the selected component in this section. After you enter an IP address, press Enter to configure multiple node IP addresses. We recommend that you use an IP address other than 127.0.0.1.

Note

The AlertManager node supports only a single IP address.

Deployment User The username is the username used to deploy the current cluster and cannot be modified. Ensure that the user exists on each host and has the corresponding directory permissions.
Software Path Configuration The default value is the installation directory of the current cluster. You can customize the software path, which must be an absolute path starting with / and can contain only letters, numbers, and special characters (-_:@/.).
Component Configuration Configure the port and password of the selected component. For more information about the ports and passwords, see Step 4: Cluster configuration in Deploy an OceanBase cluster by using the graphical interface.
More Configurations You can click the expand icon before More Settings to view the corresponding component parameters. You can use the automatically assigned values or customize the parameters.

Note

If you configure multiple nodes for the obconfigserver node in the Component Node Configuration section, you must configure the load balancer in advance and click More Configurations on this page to configure vip_address and vip_port. Otherwise, an error will be reported during the precheck.

After you configure all the parameters, click Next in the lower-right corner to go to the Precheck page.

Step 4: Precheck

On the Precheck page, view all the configuration information. If you find any issues, click Previous to modify them. After you confirm that all the configurations are correct, click Precheck to start the precheck.

If the precheck fails, you can click Auto Repair (for check items that can be automatically repaired) or click View More Solutions to go to the error code documentation and modify the configurations based on the documentation. After you modify all the errors, click Recheck to start the precheck again.

After the precheck passes, click Deploy to start the deployment of the component.

Step 5: Deploy

Where:

  • If you deployed the OBProxy component, after the deployment is successful, you can copy the displayed connection string and execute it in the CLI to connect to ODP as the root@proxysys user.

  • If you deployed a component with a graphical interface, such as Prometheus, Grafana, or Alertmanager, you can click the corresponding connection string to jump to the login page of the component. You can use the account and password displayed on the deployment page to log in.

    Note

    In an Alibaba Cloud or other cloud environment, the program may fail to obtain the public IP address and instead output the internal IP address. This IP address is not a public IP address. You need to use the correct IP address to access the graphical interface.

  • In the Deployment Report, click the expand icon before the corresponding component to view the deployment logs. When you hover over View Details in the component list, the command to view the component logs is displayed. Click the copy icon next to the command to copy it. After copying, you can execute the command on the central control node to view the log location of the component.

  • Click Copy Information to copy and save the account and password of all deployed components. Then, click Complete to exit the deployment program.

Uninstall a component

Step 1: Start the graphical interface

  1. Start the graphical interface

    Run the obd web command in the CLI to start the graphical interface. Click the displayed address to access the graphical interface.

    [admin@test001 ~]$ obd web
    start OBD WEB in 0.0.0.0:8680
    please open http://10.10.10.1:8680
    

    Note

    • The graphical interface uses port 8680 by default. You can use the obd web -p <PORT> command to specify the port. The port value must be in the range [1025, 65535].

    • In Alibaba Cloud or other cloud environments, the program may fail to obtain the public IP address and output the internal IP address. In this case, you must use the correct IP address to access the graphical interface.

    • The obd web command is bound to 0.0.0.0. In a multi-network interface deployment, you can access the graphical interface through any accessible IP address.

    • You can use the nohup or screen command to set the obd web command to run in the background.

  2. (Optional) Move the cursor to the Chinese character in the upper-right corner of the graphical interface and click the displayed language to switch between the Chinese and English interfaces.

  3. Click Start the Experience in the operation interface. In the displayed Welcome to OceanBase Deployment Wizard interface, select the Component Management module. Move the cursor to the Manage button and select the component management method based on the displayed options. Here, select Component Uninstallation.

Step 2: Uninstall the component

You can select the component to be uninstalled in the Uninstall Configuration interface. The content of the Deployment Configuration interface is as follows.

Module
Description
Uninstall Object Select the cluster from which you want to uninstall the component. Click the drop-down arrow below Cluster to display all running clusters managed by obd. Click the name of the target cluster to uninstall the component from the cluster.
Select Uninstall Component After you select the cluster, the components that can be uninstalled from the cluster are displayed here. Click the check box before the component name to select whether to uninstall the component. By default, all components are selected. Click Learn More after the component name to view the documentation of the component.

Note

Currently, you cannot uninstall obconfigserver.

After you select the component to be uninstalled, click Uninstall in the lower-right corner. In the confirmation dialog box that appears, click OK to enter the Uninstall interface.

Step 3: Uninstall

The uninstall interface displays the progress and result of the component uninstallation. You can view the Uninstall Status column of the component to determine whether the uninstallation is successful. Move the cursor to the View Running Log option in the Actions column of the component to view the uninstallation log.

The uninstallation result may be in one of the following states. You can perform the corresponding operation based on the displayed result.

Connectivity
Uninstall Status
Action
Checking Not Uninstalled No action is required. Wait for the uninstallation to complete.
Normal Uninstalling The system is uninstalling the component. Move the cursor to the View Running Log option in the Actions column to view the uninstallation log.
Uninstall Failed Move the cursor to the icon next to Uninstall Failed to view the reason for the uninstallation failure. You can perform the following operations:
  • Move the cursor to the View Running Log option in the Actions column to view the uninstallation log.
  • Click Retry in the Actions column to confirm the operation and restart the uninstallation.
  • Click Force Uninstall in the Actions column to confirm the operation and forcibly uninstall the component.
Uninstalled Move the cursor to the View Running Log option in the Actions column to view the uninstallation log.
Not Connected Uninstallable Move the cursor to the icon next to Uninstallable to view the reason for the uninstallation failure. You can click Force Remove in the Actions column to confirm the operation and forcibly uninstall the component. Note that the Force Remove operation only removes the dependency between OceanBase Database and the component, but does not uninstall the component from the host.
Removing No action is required. Wait for the system to remove the component.
Removed No action is required.

Click Complete in the lower-right corner. In the confirmation dialog box that appears, click Exit to exit the graphical interface.

Previous topic

Deploy OMS
Last

Next topic

Upgrade OCP
Next
on this page
Prerequisites
Install the component
Step 1: Start the graphical interface
Step 2: Deployment configuration
Step 3: Component configuration
Step 4: Precheck
Step 5: Deploy
Uninstall a component
Step 1: Start the graphical interface
Step 2: Uninstall the component
Step 3: Uninstall