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 Diagnostic Tool

V4.3.0
  • obdiag Overview
  • obdiag installation
  • obdiag configuration
  • One-click Cluster Inspection
    • One-click cluster inspection
    • Detailed explanation of cluster inspection indicators
  • One-click Information Gathering
    • One-click routine information collection
      • OceanBase cluster log collection
      • Host information collection
      • SQL details collection
      • Stack information collection
      • Flame Picture/Bian Que Picture Collection
      • ASH report collection
      • Collect table-related information
      • Cluster parameter collection
      • Variable collection
      • clog/slog collection
      • DBMS_XPLAN information collection
      • Core file collection
      • AWR report collection
      • obproxy log collection
      • OMS log collection
      • Collect all information
    • One-click scenario-based information collection
      • Overview
      • Collect basic cluster information
      • Collect backup problem information
      • Collect backup cleanup problem information
      • Collect clog disk full problem information
      • Collect cluster downtime problem information
      • Collect merge problem information
      • Collect CPU high problem information
      • Collect information on delay issues in primary and standby databases
      • Collect I/O problem information
      • Collect log archiving problem information
      • Collect long transaction problem information
      • Collect memory problem information
      • Collect SQL performance problem information
      • Collect PX error reporting information
      • Collect recovery problem information
      • Collect observer restart information without reason
      • Collect owner-cutting problem information
      • Collect information about hanging transaction issues
      • Collect copy imbalance problem information
      • Collect SQL error reporting information
      • Collect cluster TopSQL information
      • Collect application error information
      • Collect obproxy restart problem information for no reason
      • Collect ODP parameter information
      • Collect unspecified scenario problem information
  • One-click Diagnostic Analysis
    • One-click diagnostic analysis log
    • One-click full-link diagnostic log analysis
    • Parameter analysis (compared with default values)
    • Parameter analysis (parameter differences on different observers)
    • Analyze variables
    • Instructions for using index space analysis
    • One-click diagnostic analysis of memory
    • One-click diagnosis and analysis of queue backlog
  • One-click Root Cause Analysis
    • One-click root cause analysis
    • Root cause analysis scenario: disconnection
    • Root cause analysis scenario: card merging major_hold
    • Root cause analysis scenario: lock conflict lock_conflict
    • Root cause analysis scenario: executing DDL and reporting disk full error ddl_disk_full
    • Root cause analysis scenario: clog disk is full clog_disk_full
    • Root cause analysis scenario: log error log_error
    • Root cause analysis scenario: DDL failure ddl_failure
    • Root cause analysis scenario: Troubleshooting index build execution error index_ddl_error
    • Root cause analysis scenario: transaction disconnection scenario transaction_disconnection
    • Root cause analysis scenario: transaction execution times out and error transaction_execute_timeout
    • Root cause analysis scenario: transaction does not end and error transaction_not_ending is reported
    • Root cause analysis scenario: transaction other errors transaction_other_error
    • Root cause analysis scenario: transaction rollback error transaction_rollback
    • Root cause analysis scenario: transaction wait timeout error transaction_wait_timeout
    • Root cause analysis scenario: OMS full migration exception oms_full_trans
    • Root cause analysis scenario: OMS obcdc component analysis oms_obcdc
    • Root cause analysis scenario: suspended transaction suspend_transaction
    • Root cause analysis scenario: Unit GC exception unit_gc
    • Root cause analysis scenario: OceanBase cluster playback card
    • Root cause analysis scenario: OceanBase cluster memory explosion
    • Root cause analysis scenario: Abnormal deletion of OBServer node
    • Root cause analysis scenario: GC troubleshooting gc_troubleshooting
    • Root cause analysis scenario: Schema leak schema_leak
    • Root cause analysis scenario: partition split scheduling error split_schedule_error
    • Root cause analysis scenario: weak read problem troubleshooting weak_read_troubleshooting
    • Root cause analysis scenario: SQL execution memory is too high execute_memory_high
  • One-click Cluster Insights
    • Overview
    • Cluster overview information insights
    • Cluster node information insight
    • Cluster unit information insight
    • Cluster Zone Information Insights
    • Cluster RS Information Insights
    • Cluster tenant information insight
    • Cluster event information insight
    • Cluster lock information insight
    • Cluster topsql information insight
    • Cluster slowsql information insight
    • Cluster table information insight
    • Cluster processlist information insight
    • SQL execution plan information insights
    • Insights into database disk usage information
    • Insight on the disk usage of the specified table in the database
    • Insights into the full tenant information of the cluster
    • Cluster node CPU usage information insights
    • Internal table name fuzzy matching information insight
    • Cluster leader information insight
    • Information insights into locks held on a certain table
    • Cluster long transaction information information insight
    • Actual execution plan operator information insight
    • Memory information insights for all tenants
    • processlist Real-time session summary information insights
    • Table/index storage method information insight
    • Table NDV Information Insights
    • Table index information insight
    • Merge status display
    • clog log volume/capacity statistics
  • Plug-in file upgrade
  • Update and uninstall
  • Telemetry Mode
  • FAQ
  • Tools
    • Configuration file encryption
    • AI Intelligent Diagnosis Assistant
    • Disk IO performance detection
    • Configure verification tool
  • Release Notes
    • obdiag V4.2.0
    • obdiag V4.1.0
    • obdiag V4.0.0
    • obdiag V3.7.2
    • obdiag V3.7.1
    • obdiag V3.7.0
    • obdiag V3.6.0
    • obdiag V3.5.0
    • obdiag V3.4.0
    • obdiag V3.3.0
    • obdiag V3.2.0
    • obdiag V3.1.0
    • obdiag V3.0.0
    • obdiag V2.6.0
    • obdiag V2.5.0
    • obdiag V2.4.0
    • obdiag V2.3.0
    • obdiag V2.2.0
    • obdiag V2.1.0
    • obdiag V2.0.0
    • obdiag V1.6.2
    • obdiag V1.6.1
    • obdiag V1.6.0
    • obdiag V1.5.2
    • obdiag V1.5.1
    • obdiag V1.5.0
    • obdiag V1.4.0
    • obdiag V1.3.0

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Diagnostic Tool
  3. V4.3.0

Disk IO performance detection

Last Updated:2026-09-04 08:22:12

Function introduction
Notes
Command introduction
Usage example
Detect clog disk IO performance
Detect data disk IO performance
Use without configuration file
Interpretation of results

Since V4.0.0, obdiag supports detecting disk IO performance through the obdiag tool io_performance command. This article will introduce the specific use.

Function introduction

This command is used to detect the disk IO performance of each node in the OceanBase cluster. It supports detecting the IO performance indicators of the clog disk and data disk to help users understand the disk performance status.

Notes

  • This command requires SSH access to each OBServer node.
  • It is recommended to perform testing during low business peak periods to obtain more accurate baseline data.
  • If the await value continues to be high or util% is close to 100%, it is recommended to check the disk performance or consider expanding the capacity.

Command introduction

You can configure the -h option after the command to view command help:

obdiag tool io_performance -h

The output is as follows:

Usage: obdiag tool io_performance [options]

Options:
  --disk=DISK           disk type: clog or data
  -c CONFIG             config file path
  --config_password=CONFIG_PASSWORD
                        config password
  --inner_config=INNER_CONFIG
                        change inner config.
  --config=CONFIG       config options
  -h, --help            Show help and exit.
  -v, --verbose         Activate verbose output.

The options are explained below:

Option name
Is it required
Data type
Default value
Description
--disk No string Default is empty Disk type, configurable value is clog or data.
-c No string ~/.obdiag/config.yml Configuration file path.
--config_password No string Default is empty obdiag When using an encrypted configuration file, you need to pass in the corresponding password through this option.
--inner_config No string Default is empty obdiag's own configuration.
--config No string Default is empty Configuration of the cluster to be diagnosed by obdiag, fixed style: --config key1=value1 --config key2=value2.

Explanation

Parameters that support configuration through this option can be found in obdiag configuration.

Usage example

Detect clog disk IO performance

obdiag tool io_performance --disk=clog

Output example:

IO Performance Check for clog disk:
+-------------------+--------+--------+--------+--------+
| Node              | await  | r/s    | w/s    | util%  |
+===================+========+========+========+========+
| xxx.xxx.xxx.xxx   | 0.5ms  | 100    | 500    | 15%    |
+-------------------+--------+--------+--------+--------+
| xxx.xxx.xxx.xxx   | 0.8ms  | 120    | 480    | 18%    |
+-------------------+--------+--------+--------+--------+

Detect data disk IO performance

obdiag tool io_performance --disk=data

Output example:

IO Performance Check for data disk:
+-------------------+--------+--------+--------+--------+
| Node              | await  | r/s    | w/s    | util%  |
+===================+========+========+========+========+
| xxx.xxx.xxx.xxx   | 1.2ms  | 200    | 300    | 25%    |
+-------------------+--------+--------+--------+--------+
| xxx.xxx.xxx.xxx   | 1.5ms  | 180    | 320    | 28%    |
+-------------------+--------+--------+--------+--------+

Use without configuration file

obdiag tool io_performance --disk=clog \
    --config obcluster.servers.nodes[0].ip=xx.xx.xx.1 \
    --config obcluster.servers.nodes[1].ip=xx.xx.xx.2 \
    --config obcluster.servers.global.ssh_username=test \
    --config obcluster.servers.global.ssh_password=****** \
    --config obcluster.servers.global.home_path=/home/admin/oceanbase

Interpretation of results

Indicator
Description
await Average disk IO waiting time, in milliseconds (ms). The smaller the value, the faster the disk responds.
r/s Number of read operations per second.
w/s Number of write operations per second.
util% Disk utilization percentage. A value that is too high (such as over 80%) may indicate a performance bottleneck on the disk.

Previous topic

AI Intelligent Diagnosis Assistant
Last

Next topic

Configure verification tool
Next
on this page
Function introduction
Notes
Command introduction
Usage example
Detect clog disk IO performance
Detect data disk IO performance
Use without configuration file
Interpretation of results