Meet OceanBase AI Database, the unified database for operational data, real-time analytics, and AI. Explore ->

Meet OceanBase AI Database, the unified database for operational data, real-time analytics, and AI. Explore ->

OceanBase logo

OceanBase

A unified distributed database ready for your transactional, analytical, and AI workloads.

Product Overview
DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Resources

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS

OceanBase Cloud

OceanBase Database

Tools

Connectors and Middleware

QUICK START

OceanBase Cloud

OceanBase Database

BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Company

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

International - English
中国站 - 简体中文
日本 - 日本語
Sign In
Start on Cloud

OceanBase

A unified distributed database ready for your transactional, analytical, and AI workloads.

Product Overview
DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS
OceanBase CloudOceanBase Database
ToolsConnectors and Middleware
QUICK START
OceanBase CloudOceanBase Database
BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

Start on Cloud
编组
All Products
    • Databases
    • iconOceanBase Database
    • iconOceanBase Cloud
    • iconOceanBase Tugraph
    • iconInteractive Tutorials
    • iconOceanBase Best Practices
    • Tools
    • iconOceanBase Cloud Platform
    • iconOceanBase Migration Service
    • iconOceanBase Developer Center
    • iconOceanBase Migration Assessment
    • iconOceanBase Admin Tool
    • iconOceanBase Loader and Dumper
    • iconOceanBase Deployer
    • iconKubernetes operator for OceanBase
    • iconOceanBase Diagnostic Tool
    • iconOceanBase Binlog Service
    • Connectors and Middleware
    • iconOceanBase Database Proxy
    • iconEmbedded SQL in C for OceanBase
    • iconOceanBase Call Interface
    • iconOceanBase Connector/C
    • iconOceanBase Connector/J
    • iconOceanBase Connector/ODBC
    • iconOceanBase Connector/NET
icon

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

What is obdInstall obdQuick deployment of OceanBase DatabaseQuickly deploy OCPQuick deployment commandsCluster commandsCommand groupsImage and repository commandsTest command groupsTool commandsobdiag commandsBinlog service commandsHardware commandsLicense commandsPassword commandsTelemetry commandsUsage overviewOverviewPattern configuration rulesDeploy an OceanBase clusterDeploy OCPDeploy OMSChange componentsUpgrade OCPUpgrade OMSConfiguration fileUpgrade obdFAQError codesVersion rulesOceanBase Deploy V4.3.0OceanBase Deployment Tool V4.2.0OceanBase Deployer V4.1.0OceanBase Deployer V4.0.0OceanBase Deployer V3.6.0OceanBase Deployer V3.5.0OceanBase Deployer V3.4.0OceanBase Deployer V3.3.0OceanBase Deployer V3.2.2OceanBase Deployer V3.2.1OceanBase Deployer V3.2.0OceanBase Deployer V3.1.2OceanBase Deployer V3.1.1OceanBase Deployer V3.1.0OceanBase Deployer V3.0.1OceanBase Deployer V3.0.0OceanBase Deployer V2.10.1OceanBase Deployer V2.10.0OceanBase Deployer V2.9.2OceanBase Deployer V2.9.1OceanBase Deployer V2.9.0OceanBase Deployment Tool V2.8.0OceanBase Deployment Tool V2.7.0OceanBase Deployment Tool V2.6.2OceanBase Deployment Tool V2.6.1OceanBase Deployment Tool V2.6.0OceanBase Deployer V2.5.0OceanBase Deployer V2.4.0OceanBase Deployment Tool V2.3.1OceanBase Deployer V2.3.0OceanBase Deployment Tool V2.2.0OceanBase Deployer V2.1.1OceanBase Deployment Tool V2.1.0OceanBase Deployment Tool V2.0.1OceanBase Deployment Tool V2.0.0OceanBase Deployer V1.6.2OceanBase Deployer V1.6.1OceanBase Deployer V1.6.0OceanBase Deployer V1.5.0OceanBase Deployer V1.4.0OceanBase Deployer V1.3.3OceanBase Deployer V1.3.2OceanBase Deployer V1.3.0OceanBase Deployer V1.2.1OceanBase Deployer V1.2.0Interactive deployment of OceanBase Database Community EditionDeploy a Community Edition cluster using the obd graphical interfaceDeploy a Community Edition cluster by using an obd configuration file
OceanBase logo

The Unified Distributed Database for the AI Era.

Follow Us
Products
OceanBase CloudOceanBase EnterpriseOceanBase Community EditionOceanBase seekdb
Resources
DocsBlogWhite PaperLive DemosTraining & CertificationTicket
Company
About OceanBaseTrust CenterLegalPartnerContact Us
Follow Us

© OceanBase 2026. All rights reserved

Cloud Service AgreementPrivacy PolicySecurity
Contact Us
Document Feedback
  1. Documentation Center
  2. OceanBase Deployer
  3. V4.3.0
iconOceanBase Deployer
V 4.3.0Community Edition
Databases
  • OceanBase Database
  • OceanBase Cloud
  • OceanBase Tugraph
  • Interactive Tutorials
  • OceanBase Best Practices
Tools
  • OceanBase Cloud Platform
  • OceanBase Migration Service
  • OceanBase Developer Center
  • OceanBase Migration Assessment
  • OceanBase Admin Tool
  • OceanBase Loader and Dumper
  • OceanBase Deployer
  • Kubernetes operator for OceanBase
  • OceanBase Diagnostic Tool
  • OceanBase Binlog Service
Connectors and Middleware
  • OceanBase Database Proxy
  • Embedded SQL in C for OceanBase
  • OceanBase Call Interface
  • OceanBase Connector/C
  • OceanBase Connector/J
  • OceanBase Connector/ODBC
  • OceanBase Connector/NET
Community Edition
  • V 4.3.0
  • V 3.2.1
  • V 3.2.0
  • V 3.1.0
  • V 3.0.0
  • V 2.10.1
  • V 2.10.0
  • V 2.9.0
  • V 2.8.0
  • V 2.7.0
  • V 2.6.0
  • V 2.5.0
  • V 2.4.0
  • V 2.3.1
  • V 2.3.0
  • V 2.2.0
  • V 2.1.0
  • V 2.0.0
  • V 1.6.1

Deploy seekdb

Last Updated:2026-06-30 14:40:58  Updated
Share
What is on this page
Prerequisites
Procedure
Verify deployment results
Related operations
Sample configuration file
Related Documents

folded

Share

This topic describes how to deploy seekdb on a single server by using obd.

Prerequisites

Before you start, make sure that you meet the following conditions:

  • The server where you want to deploy the database meets the requirements described in Prepare the server and has been configured as described in Prepare for deployment.

  • You have installed obd V4.3.0 or later, and the server where obd is installed can access the server where you want to deploy the database by using SSH. For more information, see Install obd. We recommend that you install the latest version.

    Notice

    If you plan to deploy the database on an obd node, we recommend that you configure password-free SSH login for the server.

  • The obd image library contains the installation packages of the components required for deployment (seekdb and seekdb-libs), and the versions of the components are V1.2.0 or later.

    If the server where obd is installed can access the Internet, the required components will be automatically downloaded from the remote image library. If the server where obd is installed cannot access the Internet, you can download the installation package of the components from the OceanBase Download Center and execute the obd mirror clone command to upload the installation package to the local image library of obd. After the installation package is uploaded, you can execute the obd mirror list local command to view the installation packages in the local image library.

Procedure

Notice

The following steps are performed in the CentOS 7.9 x86 architecture. The steps may vary in other environments.

Interactive deployment
Deploy seekdb using the configuration file.

Execute the obd seekdb install command to start the interactive deployment process. In the interactive installation process, configure the following parameters.

  1. Select the installation mode

    Currently, three installation modes are supported: Standalone (single-node mode), Primary (primary instance mode), and Standby (standby instance mode).

    Standalone mode
    Primary instance mode
    Standby instance mode

    By default, the standalone mode is used to deploy seekdb if no options are specified.

    obd seekdb install
    

    After the command is executed, configure the following parameters for the seekdb instance:

    #Set the deployment name, which must be unique.
    Instance name [myseekdb]:
    #Enter the IP address of the machine where seekdb is to be installed. The default value is the IP address of the local machine.
    Server IP [10.10.10.1]:
    #Select the user for deployment. The default value is the current user.
    Username [admin]:
    #Set the SSH port. The default value is 22.
    SSH port [22]:
    #Enter the password of the user for deployment. The default value is empty.
    #This parameter is displayed only in non-local deployment. If you have configured password-free login, you can directly press Enter to skip this parameter.
    Password (default empty):
    #Set the installation directory of seekdb. The user specified for deployment must have read and write permissions on the directory.
    Seekdb installation directory [/home/admin/myseekdb]:
    #Set the directory for storing data such as SSTables. The user specified for deployment must have read and write permissions on the directory.
    Data directory (data_dir, optional) [/data/1]:
    #Set the directory for storing logs. The user specified for deployment must have read and write permissions on the directory.
    Redo log directory (redo_dir, optional) [/data/log1]:
    #Set the SQL port of seekdb.
    MySQL port [2881]:
    #Set the OBShell port of seekdb.
    OBShell port [2886]:
    #Specify whether to enable the automatic startup of the Seekdb service when the system boots up. The default value is no.
    #This parameter is displayed only in non-container environments. If you enable the automatic startup, make sure that the deployment user has sudo privileges. Otherwise, the deployment will fail.
    Do you want to enable the SEEK_DB_PLACEHOLDER_e6110f5f070a454dbf790bce2bff984d service to start automatically when the system boots up? (y/yes or n/no) [no]:
    

    You can specify the --primary option to deploy seekdb in the primary instance mode. When you deploy in the primary instance mode, you must configure the RPC port and enable the RPC feature to allow the standby instance to synchronize information.

    obd seekdb install --primary
    

    After the command is executed, configure the following parameters for the seekdb instance:

    #Set the deployment name, which must be unique.
    Instance name [myseekdb_primary]:
    #Enter the IP address of the machine where seekdb is to be installed. The default value is the IP address of the local machine.
    Server IP [10.10.10.1]:
    #Select the user for deployment. The default value is the current user.
    Username [admin]:
    #Set the SSH port. The default value is 22.
    SSH port [22]:
    #Enter the password of the user for deployment. The default value is empty.
    #This parameter is displayed only in non-local deployment. If you have configured password-free login, you can directly press Enter to skip this parameter.
    Password (default empty):
    #Set the installation directory of seekdb. The user specified for deployment must have read and write permissions on the directory.
    Seekdb installation directory [/home/admin/myseekdb_primary]:
    #Set the directory for storing data such as SSTables. The user specified for deployment must have read and write permissions on the directory.
    Data directory (data_dir, optional) [/data/1]:
    #Set the directory for storing logs. The user specified for deployment must have read and write permissions on the directory.
    Redo log directory (redo_dir, optional) [/data/log1]:
    #Set the SQL port of seekdb.
    MySQL port [2881]:
    #Set the RPC port of seekdb.
    RPC port [2882]:
    #Set the OBShell port of seekdb.
    OBShell port [2886]:
    #Specify whether to enable the automatic startup of the Seekdb service when the system boots up. The default value is no.
    #This parameter is displayed only in non-container environments. If you enable the automatic startup, make sure that the deployment user has sudo privileges. Otherwise, the deployment will fail.
    Do you want to enable the SEEK_DB_PLACEHOLDER_9755b1609a8743bbab80b55b63cc159d service to start automatically when the system boots up? (y/yes or n/no) [no]:
    

    You can use the --standby option to deploy the instance in standby mode. When deploying in standby mode, you must configure the information of the primary instance, that is, the instance with the identifier seekdb.

    obd seekdb install --standby
    

    After you execute the preceding command, configure the information of the instance with the identifier seekdb as described in the following example:

    # Set the deployment name. The deployment name must be unique.
    Instance name [myseekdb_standby]:
    # Select the primary instance with the identifier seekdb. If multiple instances with the identifier seekdb exist, you can use the up and down arrow keys to select one.
    ┌────────────────────────────┐
    │   Select primary cluster   │
    ├────────────────────────────┤
    │  ▸  myseekdb_primary       │
    └────────────────────────────┘
      ↑↓ move   Enter confirm   q quit
    Connect to primary (10.10.10.1:2881) ok
    # If the RPC feature is not enabled for the selected primary instance, a warning message is displayed, and an optional solution is provided.
    [WARN] Primary enable_rpc_service is not enabled.
    # You can use the up and down arrow keys to select Modify primary instance configuration and restart (Restart now) to modify the primary instance configuration and restart it, or Exit to exit the deployment process without modifying the configuration.
    ┌─────────────────────────────────────────────────────────────────────────┐
    │                              Choose action                              │
    ├─────────────────────────────────────────────────────────────────────────┤
    │  ▸  Restart now (enable in config, then stop and start primary cluster) │
    │  ○  Exit (exit without changing config)                                 │
    └─────────────────────────────────────────────────────────────────────────┘
      ↑↓ move   Enter confirm   q quit
    # To restart the primary instance, you must enter y. Otherwise, the preceding selection is repeated.
    # Restarting the primary instance may affect the running business. Proceed with caution.
    Restarting the primary instance may affect the running business. Do you want to restart it? (y/yes or n/no) [no]:
    # Enter the IP address of the server where you want to install the instance with the identifier seekdb. By default, the IP address of the current server is used.
    Server IP [10.10.10.1]:
    # Select the user for deployment. By default, the current user is used.
    Username [admin]:
    # Set the SSH port. By default, the port is 22.
    SSH port [22]:
    # Enter the password of the user for deployment. By default, the password is empty.
    # This field is displayed only when the instance is deployed on a server other than the local server. If you have configured password-free login, you can press Enter to skip this step.
    Password (default empty):
    # Set the installation directory of the instance with the identifier seekdb. Make sure that the configured user has read and write permissions for the directory.
    Seekdb installation directory [/home/admin/myseekdb_standby]:
    # Set the directory for storing data such as SSTables. Make sure that the configured user has read and write permissions for the directory.
    Data directory (data_dir, optional) [/data/1]:
    # Set the directory for storing logs. Make sure that the configured user has read and write permissions for the directory.
    Redo log directory (redo_dir, optional) [/data/log1]:
    # Set the SQL port of the instance with the identifier seekdb.
    MySQL port [2881]:
    # Set the RPC port of the instance with the identifier seekdb.
    RPC port [2882]:
    # Set the OBShell port of the instance with the identifier seekdb.
    OBShell port [2886]:
    # Specify whether to enable the automatic startup feature. By default, this feature is disabled.
    # This field is displayed only when the instance is deployed on a server other than the local server. If you want to enable the automatic startup feature, make sure that the deployment user has the sudo permission. Otherwise, an error is returned.
    Do you want to enable the Seekdb service to start automatically when the system boots up? (y/yes or n/no) [no]:
    
  2. Select the deployment mode.

    ┌───────────────────────┐
    │      Select mode      │
    ├───────────────────────┤
    │  ○  Dev (development) │
    │  ▸  Prod (production) ││
    └───────────────────────┘
      ↑↓ move   Enter confirm   q quit
    

    If you select Dev mode, the system directly outputs the configuration information. After you confirm the configuration information, the deployment starts. This mode uses fewer resources. If you select Prod mode, you must set the maximum memory value of the instance with the identifier seekdb and select a memory strategy.

    # Set the maximum memory value for seekdb. obd will generate a value range and default value based on the resources of the seekdb node.
    SeekDB Max Memory (Configurable Range[5, 31], unit: G) [28]:
    # Use the up and down arrow keys to select the memory strategy.
    ┌──────────────────────────────────────────────────────────┐
    │                     Memory strategy                      │
    ├──────────────────────────────────────────────────────────┤
    │  ▸  Balanced (Reduce memory usage when possible)         │
    │  ○  Performance (Use more memory to enhance performance) │
    └──────────────────────────────────────────────────────────┘
      ↑↓ move   Enter confirm   q quit
    
  3. Confirm the configuration

    After completing the above configuration, the program will display the configuration you just set. You need to confirm whether these configurations are correct. Here is an example:

    --- Config summary ---
      1. IP = 10.10.10.1
      2. User = admin
      3. ssh_port = 22
      4. home_path = /home/admin/myseekdb_primary
      5. data_dir = /data/1
      6. redo_dir = /data/log1
      7. mysql_port = 2881
      8. rpc_port = 2882
      9. obshell_port = 2886
      10. memory_limit = 15G
      11. memory_hard_limit = 28G
      12. datafile_size = 147G
      13. max_syslog_file_count = 1024
      14. log_disk_size = 46G
      15. auto_start = False
    Confirm config? (y/yes or n/no to modify) [yes]:
    

    Note

    • In the primary instance deployment mode, if the memory_limit value is less than 6 GB, the following warning will be displayed: memory_limit is below 6G. For a primary cluster this is small; standby sync may be slow. Consider 6G or more if you plan heavy replication..
    • When creating a standby instance, the log_disk_size of the corresponding primary instance must be at least three times the value of max(primary memory_limit, standby memory_limit). If it is less than this value, obd will automatically update the log_disk_size of the primary instance.

    You need to enter y or n at the confirmation prompt: If you enter y, the program will start deploying seekdb based on the configuration; if you enter n, you need to select the configuration to modify and set a new value. After setting the new value, all configurations will be displayed again for your confirmation. Here is an example, selecting to modify the redo_dir configuration:

    ┌───────────────────────────┐
    │    Select item to edit    │
    ├───────────────────────────┤
    │  ○  IP                    │
    │  ○  User                  │
    │  ○  ssh_port              │
    │  ○  home_path             │
    │  ○  data_dir              │
    │  ▸  redo_dir              │
    │  ○  mysql_port            │
    │  ○  rpc_port              │
    │  ○  obshell_port          │
    │  ○  memory_limit          │
    │  ○  memory_hard_limit     │
    │  ○  datafile_maxsize      │
    │  ○  max_syslog_file_count │
    │  ○  log_disk_size         │
    │  ○  auto_start            │
    └───────────────────────────┘
      ↑↓ move   Enter confirm   q back
    # Set a new value for redo_log.
    New value (current: /data/log1) [/data/log1]: /data/log2
      Updated redo_dir = /data/log2
    
  4. Deployment successful

    After the deployment of seekdb is successful, the program will display the deployment status of the instance and the corresponding connection string. The specific information is as follows:

    Start seekdb ok
    seekdb program health check ok
    Connect to seekdb 10.10.10.1:2881 ok
    obshell start ok
    obshell program health check ok
    obshell bootstrap ok
    Check RPC TLS status ok
    Connect to seekdb 10.10.10.1:2881 ok
    Wait for seekdb init ok
    +--------------------------------+
    |             seekdb             |
    +---------------+---------+------+
    | ip            | version | port |
    +---------------+---------+------+
    | 10.10.10.1    | 1.2.0.0 | 2881 |
    +---------------+---------+------+
    obclient -h10.10.10.1 -P2881 -uroot -p'********' -Doceanbase -A
    myseekdb_primary running
    

Step 1: Modify the configuration file

OBProxy provides example files. If OBProxy is installed by direct download, you can view the configuration file of OBProxy in the /usr/obd/example/seekdb directory, such as seekdb.

If obd is installed by decompressing the All-in-One installation package, you can view the example configuration files in the ~/.oceanbase-all-in-one/obd/usr/obd/example directory.

Description

  • A complete deployment example of seekdb is provided at the end of this topic in Sample configuration file. You can directly copy and modify it.

  • You need to modify the parameters in the configuration files based on your environment.

  1. Create a configuration file

    vim myseekdb.yaml
    
  2. Configure user information

    ## Only need to configure when remote login is required
    user:
      username: admin
    #   password: your password if need
      key_file: /home/admin/.ssh/id_rsa
    #   port: your ssh port, default 22
    #   timeout: ssh connection timeout (second), default 30
    

    The username is the login username for the target machine where seekdb is installed. Ensure that the user has the appropriate read and write permissions for the following directory. The password and key_file are both used for user authentication. Typically, only one of them needs to be filled in.

    Warning

    After you configure the key path, if your key does not require a password, comment out or delete the password parameter to prevent it from being considered as the key password for login, which can cause verification failure.

  3. Configure the IP address, port, and related directories of seekdb, and configure the memory-related parameters and root user password.

    seekdb:
      servers:
        - 10.10.10.1
      global:
        home_path: /home/admin/myseekdb
        data_dir: /data/1
        redo_dir: /data/log1
        mysql_port: 2881
        rpc_port: 2882
        obshell_port: 2886
        memory_limit: 12G
        memory_hard_limit: 20G
        datafile_size: 100G
        datafile_maxsize: 300G
        cpu_count: 8
        max_syslog_file_count: 1024
        log_disk_size: 30G
        enable_auto_start: false
        production_mode: false
        root_password: ********
        enable_rpc_service: true
        log_disk_utilization_threshold: 80
    

    For more information about the parameters in the configuration file, see Parameter Description in Configuration File Description. In addition, keep the following points in mind:

    • If the password is not specified in the configuration file, OBOD generates a random password automatically. After the deployment succeeds, you can run the obd cluster edit-config command to view the corresponding parameter in the configuration file to obtain the password.

    • Setting enable_auto_start to true enables the observer process to start automatically at boot. This feature requires the deployment user to have sudo privileges and the deployment environment to be non-container based.

Step 2: Deploy an instance of seekdb

Note

For more information about the commands in this topic, see seekdb Commands.

  1. Deploy the instance of seekdb.

    [admin@test001 ~]$ obd seekdb deploy myseekdb -c myseekdb.yaml
    

    The example uses a deployment name of myseekdb and a configuration file name of myseekdb.yaml as placeholders. You can customize the deployment name and specify the required configuration file based on your specific needs.

    This command checks if the directory in the configuration file is empty. If not, it will report an error. If you are sure that all content in the directory can be deleted, you can add the -f option to forcibly empty the directory.

  2. Start the seekdb instance

    [admin@test001 ~]$ obd seekdb start myseekdb
    

    After the instance is started, the deployment status and corresponding connection strings are output, specifically as follows:

    Wait for seekdb init ok
    +--------------------------------+
    |             seekdb             |
    +---------------+---------+------+
    | ip            | version | port |
    +---------------+---------+------+
    | 10.10.10.1    | 1.2.0.0 | 2881 |
    +---------------+---------+------+
    obclient -h10.10.10.1 -P2881 -uroot -p'********' -Doceanbase -A
    myseekdb running
    

Verify deployment results

  1. Go to the list of the seekdb instances.

    Execute the obd seekdb list command to view the instance list of the seekdb cluster. The output shows a running instance named myseekdb_primary of the seekdb type.

    +--------------------------------------------------------------------------------+
    |                              SeekDB Cluster List                               |
    +------------------+-------------------------------------------+-----------------+
    | Name             | Configuration Path                        | Status (Cached) |
    +------------------+-------------------------------------------+-----------------+
    | myseekdb_primary | /home/admin/.obd/cluster/myseekdb_primary | running         |
    +------------------+-------------------------------------------+-----------------+
    
  2. View the status of the seekdb instance.

    [admin@test001 ~]$ obd seekdb display myseekdb_primary
    

    Output is as follows:

    Get local repositories and plugins ok
    Open ssh connection ok
    Connect to seekdb 10.10.10.1:2881 ok
    Wait for seekdb init ok
    +--------------------------------+
    |             seekdb             |
    +---------------+---------+------+
    | ip            | version | port |
    +---------------+---------+------+
    | 10.10.10.1    | 1.2.0.0 | 2881 |
    +---------------+---------+------+
    obclient -h10.10.10.1 -P2881 -uroot -p'********' -Doceanbase -A
    
  3. Connect to the instance of seekdb

    You can copy the connection string displayed in obd seekdb display to connect to the instance of seekdb.

    obclient -h10.10.10.1 -P2881 -uroot -p'********' -Doceanbase -A
    

    The output is as follows, indicating that the root user has successfully logged in to the instance named seekdb.

    Welcome to the OceanBase.  Commands end with ; or \g.
    Your OceanBase connection id is 3221489761
    Server version: OceanBase 4.3.5.3 seekdb (r1.2.0.0) (Built 200000212026032314-50f34cacb66d188d8fb030696f4c2e987d1648c3 Mar 23 2026)
    
    Copyright (c) 2000, 2018, OceanBase and/or its affiliates. All rights reserved.
    
    Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
    
    obclient(root@(none))[oceanbase]>
    

Related operations

You can run the following commands to manage the seekdb instance deployed by using obd. For more information, see seekdb commands.

  • View the list of seekdb instances.

    obd seekdb list
    
  • View the status of the seekdb instance named myseekdb.

    obd seekdb display myseekdb
    
  • Modify the parameters of the seekdb instance.

    obd supports the obd cluster command group to manage seekdb instances. You can run the following command to open the configuration file and modify the seekdb instance configuration.

    obd cluster edit-config myseekdb
    

    After you modify the configuration and save the changes, obd will inform you how to make the changes take effect. You can copy the command output by obd. The output after you save the changes is as follows:

    Search param plugin and load ok
    Search param plugin and load ok
    Parameter check ok
    Save deploy "myseekdb" configuration
    Use `obd cluster reload myseekdb` to make changes take effect.
    

    You can copy and run the obd cluster reload myseekdb command in the output to make the changes take effect.

  • Stop the seekdb instance named myseekdb.

    obd seekdb stop myseekdb
    
  • Destroy the seekdb instance named myseekdb.

    obd seekdb destroy myseekdb
    

Sample configuration file

user:
  username: admin
  #password: ********
  key_file: /home/admin/.ssh/id_rsa
seekdb:
  servers:
    - 10.10.10.1
  global:
    home_path: /home/admin/myseekdb
    data_dir: /data/1
    redo_dir: /data/log1
    mysql_port: 2881
    rpc_port: 2882
    obshell_port: 2886
    memory_limit: 12G
    memory_hard_limit: 20G
    datafile_size: 100G
    datafile_maxsize: 300G
    cpu_count: 8
    max_syslog_file_count: 1024
    log_disk_size: 30G
    enable_auto_start: false
    production_mode: false
    root_password: ********
    enable_rpc_service: true
    log_disk_utilization_threshold: 80

Related Documents

  • Create a standby instance
  • Configuration file description
  • Role switching and decoupling

Previous topic

Deploy an OceanBase cluster
Last

Next topic

Deploy obconfigserver
Next
What is on this page
Prerequisites
Procedure
Verify deployment results
Related operations
Sample configuration file
Related Documents