Before deploying OCP, you must create the MetaDB component for OCP in OAT. If you want to use an already deployed MetaDB, you can refer to Take over MetaDB to take over MetaDB into OAT.
This section describes how to create MetaDB in OAT.
Prerequisites
Before creating MetaDB, confirm the following information:
- You have installed OAT and logged in using a super administrator or O&M personnel account. For more information, see Install OAT.
- You have added the server where MetaDB is to be installed. For more information, see Add a server.
- Your server meets the resource requirements for installing MetaDB.
Procedure
Step 1: Go to the Create MetaDB page
Log in to OAT.
In the left navigation bar, click Product Service > Components.
On the Component Management page, click Create Component in the upper-right corner and select Create MetaDB.
Step 2: Configure basic information
The basic information required for MetaDB is as follows:
Parameter |
Description |
|---|---|
| MetaDB Image | Docker image file of MetaDB. Click Manage Image Files in the drop-down list to add the image file via Local Scan or Remote Connection in the pop-up panel.
|
| Component Name | The name of the component. It must be unique and cannot duplicate other component names. The default name is metadb. |
| Custom Zone | To enable custom zones, you need to specify the zone name, IDC, server, and Root Server location.
NoteThis parameter and the Server parameter are mutually exclusive. After you enable custom zones, the server parameters will be automatically hidden. |
| Configure the arbitration service | You can freely enable or disable arbitration service. When enabling it, you can select an existing arbitration service. If no arbitration service has been created in advance or no existing one is selected, you can also click the Create Arbitration Service button to create a new one by entering the relevant information.
Note
|
| Server | The IP address of the server on which you want to install MetaDB. If you need to deploy a multi-node MetaDB, you can select multiple IP addresses. In this case, one instance of MetaDB will be installed on each selected server. |
| CPU | The number of CPU cores available to the MetaDB on the server. The default value is 32. |
| Memory | The memory available for MetaDB on the server, which is 90 GiB by default. |
| The name of the MetaDB cluster. | The cluster name of MetaDB. |
| root@sys password | The password of the root user in the sys tenant. |
Step 3 (Optional): Configure the installation path
The directory information to be configured is as follows:
Parameter |
Description |
|---|---|
| Installation Directory | The installation path of MetaDB. Default value:/home/admin/oceanbase, which supports custom directories. |
| Data Directory | Data storage path of MetaDB. Default value:/data/1, supporting custom directories. |
| Log Directory | Log storage path of MetaDB. Default value:/log/1, supporting custom directories. |
| Backup Directory | Optional. The backup directory of the MetaDB. The default value is empty. You can specify a custom directory. |
Step 4 (Optional): Configure startup parameters
The startup parameters to be configured are as follows:
Parameter |
Description |
|---|---|
| MySQL Port | MySQL port of MetaDB. Default value: 2881. |
| RPC Port | The RPC port of MetaDB, with a default value of 2882. |
| OBProxy Service Port | The service port of OBProxy, with a default value of 2883. |
| SSH Port | The SSHD port in the MetaDB container. Default value: 2022. OCP deploys the OCP Agent by connecting to this SSHD port. |
| Root Password | The password of the root user in the MetaDB container. |
Note
- The CPU and memory resources required for MetaDB are the cumulative values of the resources for MetaDB, MonitorDB, the sys tenant, system_memory, and OBProxy. When allocating resources to MetaDB, it is recommended that you reserve a margin in addition to the required resources (the sys tenant itself also occupies certain resources).
- When configuring the installation path for MetaDB, ensure that the data directory, installation directory, and log directory are empty, and the user owning these directories is admin.
- In the same MetaDB cluster, ensure that the hardware architecture of the images remains consistent (currently, OAT does not support heterogeneity).
Step 5: Submit the creation task
After configuring MetaDB, click Submit. If your configuration is incorrect, you can click Reset to restore the default configuration with one click.
After submitting the creation of MetaDB, go to System and Security > Task Center, and click the task name to view detailed task information.