OceanBase
English日本語简体中文
ドキュメントホーム
製品
エコシステム
リリース

データベース

OceanBase CloudOceanBaseデータベース

ツール

OceanBase Cloud PlatformOceanBase移行サービス(OMS)OceanBaseデベロッパーセンターOceanBase Admin Tool

データベース

OceanBase CloudOceanBaseデータベース

ツール

OceanBase Cloud PlatformOceanBase移行サービス(OMS)OceanBaseデベロッパーセンターOceanBase Admin Tool
OceanBase CloudOceanBaseデータベース

OceanBaseデータベース

コミュニティ
  • OceanBaseデータベース Community版 V4.4.2
  • OceanBase Database Community Edition V4.3.5

PDF をダウンロード

このページには現在中国語/日本語版がなく、英語版を表示しています。
ドキュメントフィードバック
  1. ドキュメントセンター
  2. OceanBaseデータベース
  3. master

OceanBase Database Community Edition V4.1.0

最終更新:2026-09-03 02:29:52

V4.1.0 Beta
Version information
Overview
Features
Performance report
Compatibility changes
Note
Supported components
Limitation
V4.1.0
Version information
Overview
Bug fixes
Note
V4.1.0 BP1
Version information
Overview
Bug fixes
Note

V4.1.0 Beta

Version information

  • Release date: March 20, 2023
  • Version: V4.1.0

Overview

OceanBase Database Community Edition V4.1 leverages the upgraded architecture of V4.0 and is specifically tailored towards public cloud and open source scenarios. In addition to its rich variety of features, this version is further optimized to achieve improved compatibility with MySQL 8.0, as well as enhanced performance and ease of use at a lower cost. This version is also designed to support large-scale replication, and therefore can be comprehensively commercialized.

This version comes with a range of powerful updates designed to significantly enhance its core capabilities, including:

  • Enhancements

    SQL statement-level resource isolation, tenant-level input/output operations per second (IOPS) isolation, and the Latin1 character set are supported.

  • Compatibility with MySQL

    Compatibility with MySQL 8.0 in terms of functions, variables, and SQL modes is improved. Geographic information system (GIS) data types are supported.

  • Improved performance

    • Transactional processing (TP) performance:

      • Compared with OceanBase Database Community Edition V4.0, our new version improves the comprehensive read/write performance by about 40% when running the Sysbench benchmark with 1024 threads.
      • This version also improves the performance by about 8% in terms of transactions per minute (tpmC) when running the TPC-C benchmark with 1000 warehouses.
    • Analytical processing (AP) performance:

      • Compared with OceanBase Database Community Edition V4.0, our new version improves the TPC-H query performance by about 17% when executing 22 SQL statements sequentially with 100 GB of data.
      • The TPC-DS query performance is improved. This version can execute 99 SQL statements sequentially with 100 GB of data in just 161 seconds.
    • Data import performance: The speed of importing a 74 GB lineitem table in bypass mode to an OBServer node with the c6a.12xlarge specification (48 vCPUs, 96 GB of memory) can now reach up to 165MB/s.

    • The routing of distributed transactions is optimized based on OceanBase Database Proxy (ODP), improving the performance of distributed transactions.

    • OceanBase Database Community Edition V4.1 also improves the performance of the NESTED LOOP JOIN operator, the execution of Index Skip Scan, the parallel execution of the TRUNCATE TABLE statement, and the compilation feedback.

  • Enhanced stability

    The upper limit on the storage size of LOBs is increased.

  • Enhanced high availability

    Primary and standby tenants based on archived logs are supported, achieving a recovery time objective (RTO) of less than 8s in more scenarios.

  • O&M capabilities

    • Online upgrades of V4.0 series are supported.

    • Statistics are collected in real time.

    • The log system and readability are optimized.

    • Persistence and storage are optimized: Adaptive compactions are supported and space optimization is implemented for small tables.

  • Product form

    A standalone edition is released.

Features

Enhancements

  • SQL statement-level resource isolation is supported.

    We noticed that our customers often require more fine-grained control over resource isolation. For example, they use different resource specifications for different SQL statements and isolate resources of different users in the same tenant. This helps application systems allocate and isolate resources for online analytical processing (OLAP) and online transactional processing (OLTP) services, minimizing the mutual impact between services.

    With OceanBase Database Community Edition V4.1, you can create resource groups and bind users to them. When you execute a business SQL statement, the system determines the corresponding resource group based on predefined SQL rules. You can use the DBMS_RESOURCE_MANAGER package to define business resource isolation strategies. Currently, only CPU resource isolation in MySQL mode is supported.

  • Tenant-level IOPS isolation is supported.

    OceanBase Database offers tenant-level isolation since V4.0. That is, resources are distributed among tenants based on their allocated units and I/O categories. This way, each task within a tenant utilizes only its assigned resources and does not compete with other tasks for resources. However, customized resource isolation for some I/O categories based on tasks are not supported. Also, resources cannot be further isolated for different users within the same tenant. To achieve unified resource isolation, we integrated both I/O and CPU resources into the Resource Manager framework on the UI.

    With OceanBase Database Community Edition V4.1, you can customize isolation strategies for I/O resources by using the DBMS_RESOURCE_MANAGER package. Specifically, you can define an isolation plan by setting the MIN_IOPS, MAX_IOPS, and WEIGHT_IOPS parameters in the CREATE_PLAN_DIRECTIVE package function. Note that you can define IOPS isolation plans for both Oracle and MySQL tenants.

  • The Latin1 character set is supported.

    As the number of OceanBase Database users continues to grow, we have noticed an increase in demand for the use of the Latin1 character set. By adding support for this character set in OceanBase Database V4.1, we are simplifying project migration that would otherwise require complex character set conversions. In MySQL mode, we support both latin1_bin and latin1_swedish_ci collations, while in Oracle mode, only latin1_bin is supported.

Compatibility with MySQL

  • Compatibility with MySQL 8.0 in system functions, variables, and SQL modes is improved.

    Most features of MySQL 5.7 are supported in OceanBase Database V4.0 and earlier versions. As more experienced MySQL users try OceanBase Database public cloud and community editions, we decide to further enhance the compatibility with MySQL 8.0 in OceanBase Database V4.1. Supported features include:

    • System functions
      • Character operation functions: BIN_TO_UUID(), CHARACTER_LENGTH(), LOAD_FILE(), IS_UUID(), UUID_TO_BIN(), and OCTET_LENGTH().
      • Datetime functions: ADDTIME() and DAYNAME().
      • Encryption and decryption functions: DECODE(), DES_DECRYPT(), DES_ENCRYPT(), ENCODE(), and ENCRYPT().
      • Performance information functions: FORMAT_BYTES() and FORMAT_PICO_TIME().
      • Information functions: CURRENT_ROLE() and ICU_VERSION().
      • Analytic functions: BIT_AND(), BIT_OR(), and BIT_XOR().
      • Other functions: NAME_CONST().
    • SQL modes
      • Independent SQL modes: REAL_AS_FLOAT and TIME_TRUNCATE_FRACTIONAL.
      • Composite SQL modes: ANSI, DB2, MAXDB, MSSQL, ORACLE, POSTGRESQL, and TRADITIONAL.
    • Information schemas
      • View compatibility: View fields in OceanBase Database are the same as those in MySQL 8.0, but the field data types, widths, and constraints are adjusted for compatibility. For example, OceanBase Database provides the following views: VIEW_TABLE_USAGE, VIEWS, TABLES, STATISTICS, ENGINES, TABLE_CONSTRAINTS, REFERENTIAL_CONSTRAINTS, CHECK_CONSTRAINTS, PARAMETERS, ROUTINES, and PARTITIONS.
      • Performance improvement: The overall query performance of system views such as STATISTICS is improved based on local table indexes.
    • Float(m, d): OceanBase Database V4.1 is fully compatible with the data types and precisions in MySQL 8.0.
  • GIS data types are supported.

    GIS provides storage, computing, and indexing capabilities for spatial objects such as points, lines, planes, and complex spatial objects. GIS is widely applied in the transportation industry and can help quickly build spatial computing capabilities. OceanBase Database supports GIS since V3.2.4 and adopts the quadtree-based indexing solution. We also provide robust support for GIS data types of MySQL 8.0, the management and caching of spatial reference system (SRS) metadata, quadtree-based spatial indexes, single-value types, and multi-value types. Single-value types include GEOMETRY, POINT, LINESTRING, and POLYGON, and multi-value types include MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, and GEOMETRYCOLLECTION. OceanBase Database V4.1 also implements the spatial computing functions commonly used in MySQL 8.0.

Improved performance

  • The data import performance is improved.

    Data import performance is a crucial metric in the field of OLAP. Applications for data analysis and big data are typically associated with large data volumes. In the AP field, the capability to rapidly import business data from TXT or CSV formats into a database and provide external queries and analysis is a key competitive advantage that influences customers' decision-making.

    When a database system imports data, the SQL layer parses the data received from the client, checks for errors, routes and forwards it to its destination. The data is then put into transactions and stored. However, this process has some limitations: the data is filtered and parsed row by row by the SQL layer, leading to an accumulation of logs that can slow down the system. To address this issue, OLAP databases use the bypass import technology to preserve resources and cut costs in SQL processing. By using this method, the data can be saved directly to the disk.

    OceanBase Database V4.1 uses the bypass import technology to streamline the data loading path by skipping modules such as the SQL layer, transaction module, and MemTables, to directly persist data to SSTables, thereby significantly accelerating data import. To use the bypass capability, you must add a hint in the LOAD DATA statement, for example, load data /*+ direct(true , 1024) parallel(64) */ infile '/data/1/hits.tsv' into table hits Fields Terminated By '\t';. You can query the V$SESSION_LONGOPS view for the import progress. Primary key conflict and error tolerance processing is supported in different modes. At present, only CSV data files are supported. If you import a 74-GB lineitem table in bypass mode to an OBServer node with the c6a.12xlarge specification, which provides 48 vCPUs and 96 GB of memory, the import speed can reach 165 MB/s.

  • The routing of distributed transactions is optimized based on ODP, improving the performance of distributed transactions.

    During business data modeling, transactions are generally processed on the same data node to avoid compromising the performance due to cross-node access of distributed transactions. In earlier versions of OceanBase Database, only requests in the same transaction can be processed on the same OBServer node. Therefore, ODP cannot route SQL queries based on the locations of data to access. This increases the latency in SQL processing within distributed transactions, thereby compromising the performance. During performance testing, the execution sequence of SQL statements must be adjusted to optimize the performance. Much time and energy are consumed to reduce the negative impact caused by the routing of distributed transactions on the performance.

    OceanBase Database V4.1 optimizes routing for distributed transactions. ODP synchronizes the running status of transactions to OBServer nodes. Not all the running status information needs to be sent to the coordinator. A route can be calculated for each SQL statement. This ensures that SQL requests can be executed on any OBServer node in the cluster, thereby avoiding unnecessary processing latency. You can specify the enable_distributed_route parameter of ODP to enable routing optimization for distributed transactions, which is enabled by default. At present, routing optimization is not supported for eXtended Architecture (XA) transactions.

  • Other performance improvements:

    • The performance of the multistage NESTED LOOP JOIN operator is improved by about 10 times in specific Group Rescan scenarios.
    • The execution of Index Skip Scan is optimized. When the NDV operator is used to calculate more than 0.5 million rows of data, the performance can be improved by about 10 times.
    • The parallel execution of the TRUNCATE TABLE statement is optimized, improving the statement execution efficiency by about 10 times.

Enhanced stability

  • The upper limit on the storage size of LOBs is increased by using DBMS_LOB.

    In earlier versions of OceanBase Database, the size of a stored LOB is limited to 48 MB. This poses a forcible restriction on the use of LOBs. Through the architectural upgrade in OceanBase Database V4.1, the storage layer splits an LOB macroblock into multiple LOB metadata records for storage. When the LOB macroblock needs to be fetched, these metadata records are aggregated into a continuous buffer, which is then returned to the SQL layer for processing. This breaks the limit on the data storage size and extends the LOB size to 512 MB by using regular SQL statements. In Oracle mode, the LOB size can be extended to the TB level by using the DBMS_LOB package.

Enhanced high availability

  • Primary and standby tenants based on archived logs are supported.

    To continuously improve database high availability is one of objectives in the design of OceanBase Database. Based on the distributed architecture and multi-replica data management mechanism, OceanBase Database can meet the high availability requirements of business systems in most scenarios. However, for industries such as banking and insurance that have extremely high requirements on the high availability of databases, when a single cluster is deployed in three IDCs across two regions for geo-disaster recovery, services may still become unavailable due to poor network communication across regions. Therefore, OceanBase Database provides the tenant-level primary/standby solution to resolve the issues in cross-region geo-disaster recovery.

    In earlier versions of OceanBase Database, the primary/standby cluster solution is used based on the cluster-level log transmission strategy. In this strategy, the primary and standby clusters must be able to detect the log synchronization status of each other, and log coupling exists between tenants. In OceanBase Database V4.1, we offer a tenant-level primary/standby solution, where the primary and standby tenants are fully decoupled and unaware of each other. Archive logs are asynchronously synchronized by using a third-party network file system (NFS) or object storage service (OSS). The primary and standby tenants support resumable transmission of logs, switchover, and failover. In the tenant-level primary/standby solution, an OceanBase cluster can contain both primary and standby tenants to help business applications achieve more balanced resource utilization.

  • The RTO is reduced to less than 8s in more scenarios.

    Compared with OceanBase Database V4.0, OceanBase Database V4.1 is architecturally upgraded and optimized in fault detection for the distributed architecture and partition election capabilities, aiming to achieve an RTO of less than 8s in most scenarios. Specifically:

    • If the primary OBServer node crashes due to a fault, the standby OBServer node works with ODP to recover services.
    • If the log disk or data disk of the primary OBServer node becomes faulty, the primary node returns an error but does not go offline. The replicas on this node are migrated to a functioning node and a new leader is elected to provide services. In this case, the number of available replicas decreases and the faulty node needs to be manually recovered.

Enhanced O&M capabilities

  • Online upgrades of V4.0 series are supported.

    OceanBase Database V4.0 is a major upgrade that introduces significant architectural changes, including updates to storage data, internal tables, views, parameters, and some functionality. Therefore, OceanBase Database cannot be directly upgraded from V3.x to V4.0. We recommend that you use OceanBase Migration Service (OMS) for data logic migration and upgrading instead. However, from V4.1, OceanBase Database provides new capabilities, including system data compatibility, support for physical online upgrades, and uninterrupted project upgrades. These capabilities aim to reduce upgrade complexity and costs while promoting OceanBase Database V4.1 in more scenarios.

    OceanBase Database V4.1 adopts the rotating upgrade strategy.

    1. After an upgrade is initiated, the cluster enters the hybrid deployment state. The system replaces the binary programs of OBServer nodes by zone and exits the hybrid deployment state until the binary programs of all nodes are replaced. At this time, binary programs of the later database version host the data and behaviors of the earlier version in compatibility mode.
    2. After you run an upgrade command in a tenant, the system verifies and corrects the variables, system tables, and data. You must run the same upgrade command for all the tenants in the cluster one by one to finish the overall upgrade of the cluster. We recommend that you use OceanBase Cloud Platform (OCP) to upgrade your cluster online.

    OceanBase Database V4.1 supports the following upgrade scenarios:

    • Online cluster upgrades
    • Primary/Standby cluster upgrades. You can upgrade the primary and standby clusters separately. We recommend that you upgrade the standby cluster before the primary cluster. Before the upgrade, use the switchover command to adjust the state of the tenants in the cluster to ensure that they are in the consistent state.
    • Continuous upgrades since OceanBase Database V4.0, including the upgrades of features and patches.
    • Tenant-level upgrades. We recommend that you upgrade all tenants in the cluster to the same version.
    • Note that upgraded OBServer nodes do not support rollbacks. Therefore, we recommend that you back up the data and binary programs before the upgrade.

    Do not perform the following operations during the upgrade, which are allowed after the upgrade is completed:

    • DDL operations
    • Major freezes
    • Migration, replication, and load balancing
    • Physical backup and restore
    • Switchover and failover
    • Tenant creation
  • The log system and readability are optimized.

    OceanBase Database V4.1 systematically analyzes and optimizes log generation in the following aspects:

    • Definition of log levels: The DIAG log level is added. WARN and ERROR logs that are imperceptible to users are classified as DIAG logs. The levels are adjusted for O&M-oriented WARN and ERROR logs that need to be retained.

      Current log level
      Intended audience
      Definition
      Original log level
      ERROR DBA or general users Exceptions that cause the OBServer node to be unable to provide normal services. For example, the disk is full or the listening port is occupied. For another example, an internal check error is returned in the background, such as 4377(dml defensive check error) or 4103 (data checksum error). In this case, manual intervention is needed. /
      WARN DBA or general users Unexpected scenarios where the OBServer node can provide services but its behaviors are not as expected. For example, a write throttling alert is generated. /
      INFO DBA or general users Information about system changes. INFO
      EDIAG R&D engineers Error diagnosis information indicating unexpected logic errors, such as unexpected function arguments. ERROR
      WDIAG R&D engineers Warning diagnosis information indicating expected errors, such as failures returned by functions. WARN
      TRACE R&D engineers Task-level debugging information. TRACE
      DEBUG R&D engineers Detailed debugging information. DEBUG
    • Error code association: Error messages are classified and error codes are improved. A response error code is defined for each warning and error. You can retrieve documents based on an error code to find the solution.

    • Throttling by error code: WDIAG logs are throttled by error code. For throttled logs, only the error code and the number of throttled logs are displayed. The diag_syslog_per_error_limit parameter is added for controlling this throttling feature. By default, 200 DIAG logs per second are allowed for each error.

    • Log file self-description: The server address, host type, CPU type, operating system version, OBServer version, and time zone are recorded in the header of each log file.

  • Views are standardized. Views and internal tables are redesigned. Totally 73 standard views are provided. We recommend that you query views for information such as the metadata of OceanBase Database.

  • Statistics are collected in real time.

    The accuracy of statistics is the basis for the optimizer to generate a proper execution plan. Earlier versions of OceanBase Database already support statistics collection in the following ways:

    • Use the DBMS_STATS package or the ANALYZE command to manually trigger statistics collection.
    • Configure scheduled tasks to automatically collect statistics.
    • Automatically collect statistics when the data amount exceeds the specified threshold.

    OceanBase Database V4.1 supports online statistics collection. You can enable this feature by using the _optimizer_gather_stats_on_load system variable or hints. If the business system supports the CTAS or INSERT statement, OceanBase Database updates incremental statistics in real time. This avoids system overheads caused by full table scans performed in regular statistics collection.

  • Data persistence and storage are optimized.

    • Adaptive compaction: A compaction consumes a large number of I/O operations and CPU resources. Therefore, different compaction strategies are needed in different business scenarios. In the log-structured merge (LSM) storage system, the core objective of compactions is to achieve an optimal balance among write amplification, read amplification, and space amplification. In the adaptive compaction strategy, the system collects statistics about and analyzes the historical minor compactions and query operations performed on a table to extract the characteristics of the table, determines whether to schedule a major compaction for this table based on these characteristics, and completes a major compaction that is imperceptible to users.

    • Table space optimization: If a small table is split into many partitions, storage amplification appears in macroblock storage. This is prone to result in insufficient disk space when a large number of partitions exist. Multiple small SSTables are stored in a physical macroblock for compaction and storage. This achieves a utilization of about 4% and a fragment ratio of about 1.5% for the macroblock when a small table is split into many partitions, significantly improving the disk utilization.

Product form

  • A standalone edition is released.

    Based on the integrated architecture for standalone and distributed modes of OceanBase Database V4.0, we released a standalone edition for OceanBase Database V4.1. The standalone edition can be deployed by using OCP or OceanBase Deployer (OBD), enabling independent software vendors (ISVs), small-sized customers, and community users to quickly get started with the new features of OceanBase Database V4.1. If the standalone edition can no longer meet your project requirements, business requirements, or high availability requirements, you can upgrade the standalone edition to a distributed edition online with ease.

Performance report

Test environment specifications

Resource
Specifications
CPU platform architecture x86_64
ECS type ecs.g7.8xlarge
Computing resource 32 cores
Memory 128 GB
Disk resource 500 GB ESSD
Operating system CentOS Linux release 7.9.2009 (Core)

Tested versions

Product
Version information
OceanBase Database V4.1 OBServer (OceanBase_CE 4.1.0.0)
REVISION: 100000172023031416-6d4641c7bcd0462f0bf3faed011803c087ea1705
BUILD_TIME: Mar 14 2023 16:53:58
ODP V4.1 ODP (OceanBase 4.1.0.0 1)
REVISION: 5617-local-e6798c479feaab9f9a60b89f87e4df5e284250b6
BUILD_TIME: Mar 11 2023 21:42:11
OceanBase Database V4.0 OBServer (OceanBase_CE 4.0.0.0)
REVISION: 103000022023011215-05bbad0279302d7274e1b5ab79323a2c915c1981
BUILD_TIME: Jan 12 2023 15:28:27
ODP V4.0 ODP (OceanBase 4.0.0 5)
REVISION: 1-local-9d5c90e562c61d9fcf8894993187aa20239db47e
BUILD_TIME: Oct 28 2022 23:01:19

Sysbench OLTP benchmark

Test plan:

  1. Use OBD to deploy an OceanBase cluster. Install ODP on a separate server with a specification of ecs.c7.16xlarge, which provides 64 CPU cores and 128 GB of memory, and install Sysbench tools on another server to avoid resource contention.
  2. Deploy the cluster in the 1-1-1 architecture, where the cluster has three zones and each zone has one OBServer node. After successful deployment, create the tenant and users required for running the Sysbench benchmark. The sys tenant is a built-in system tenant used for managing the cluster. Do not use the sys tenant to run the benchmark. Set primary_zone to RANDOM for the tenant, which indicates that the leader of new table partitions is randomly assigned to one of the three servers.
  3. Launch the Sysbench client and perform the point_select, read_write, read_only, and write_only tests.
  4. Set the --time parameter to 60s for each round of test. The number of threads can be 32, 64, 128, 256, 512, or 1,024.
  5. The test dataset consists of 30 non-partitioned tables with 1 million rows of data. To be specific, set --tables to 30 and --table_size to 1000000.

Tenant specifications:

  • MAX_CPU = 26
  • MEMORY_SIZE = 70 GB

Results:

Point select performance

Threads
V4.0 QPS
V4.0 95% Latency (ms)
V4.1 QPS
V4.1 95% Latency (ms)
32 139594.87 0.26 135146.05 0.27
64 257088.19 0.29 251219.37 0.30
128 453625.18 0.34 431564.13 0.36
256 746710.21 0.50 686271.21 0.55
512 964910.06 0.81 920502.51 0.92
1024 988444.97 1.64 972018.58 1.76

Read-only performance

Threads
V4.0 QPS
V4.0 95% Latency (ms)
V4.1 QPS
V4.1 95% Latency (ms)
32 100505.96 6.43 117325.66 4.65
64 189356.32 6.55 214733.98 5.18
128 326115.21 7.43 370499.19 6.09
256 479483.89 10.46 572924.33 8.13
512 584193.84 19.29 705032.91 13.95
1024 561898.43 70.55 755182.87 28.16

Write-only performance

Threads
V4.0 QPS
V4.0 95% Latency (ms)
V4.1 QPS
V4.1 95% Latency (ms)
32 38301.16 6.43 42329.95 5.37
64 71365.18 6.91 74408.79 6.09
128 117430.28 8.13 126026.90 Jul. 30
256 182082.02 10.84 197493.43 9.56
512 252286.87 16.71 288284.95 13.95
1024 290982.27 31.37 354554.10 25.74

Read/Write performance

Threads
V4.0 QPS
V4.0 95% Latency (ms)
V4.1 QPS
V4.1 95% Latency (ms)
32 63498.13 12.30 74857.82 9.39
64 120362.58 12.52 138795.77 10.27
128 197802.61 15.55 234340.23 12.08
256 303103.47 20.37 365657.91 16.12
512 383006.31 33.12 479109.44 25.74
1024 389587.53 104.84 561333.10 48.34

TPC-C benchmark test with BenchmarkSQL

Test plan:

  1. Use OBD to deploy an OceanBase cluster. Deploy ODP and the TPC-C tools on the same server to avoid insufficient stress on the client.
  2. Deploy the OceanBase cluster in the 1-1-1 architecture, where the cluster has three zones and each zone has one OBServer node. After successful deployment, create the tenant and users required for running the TPC-C benchmark. The sys tenant is a built-in system tenant for managing the cluster. Do not use the sys tenant to run the benchmark. Set primary_zone to RANDOM for the tenant.

Tenant specifications:

  • MAX_CPU = 26
  • MEMORY_SIZE = 70 GB

Software versions:

mysql-connector-java-5.1.47

BenchmarkSQL V5.0

Test configuration:

  • warehouses = 1000
  • loadWorkers = 40
  • terminals = 800
  • runMins = 5
  • newOrderWeight = 45
  • paymentWeight = 43
  • orderStatusWeight = 4
  • deliveryWeight = 4
  • stockLevelWeight = 4

Results:

V4.0
V4.1
tpmC (NewOrders) 307,021.0 332559.26
tpmTOTAL 682,517.67 738374.78

TPC-H benchmark test

Test plan:

  1. Use OBD to deploy an OceanBase cluster. Deploy the TPC-H client on a server for stress testing. You do not need to deploy ODP. You can connect to any server during testing.
  2. Deploy the OceanBase cluster in the 1-1-1 architecture, where the cluster has three zones and each zone has one OBServer node. After successful deployment, create the tenant and users required for running the TPC-H benchmark. The sys tenant is a built-in system tenant for managing the cluster. Do not use the sys tenant to run the benchmark. Set primary_zone to RANDOM for the tenant. Load the data, sequentially execute 22 SQL queries, and take the average value.
  3. Size of the test dataset: 100 GB.

Tenant specifications:

  • MAX_CPU = 26
  • MEMORY_SIZE = 70 GB

Results:

Query
V4.0 (s)
V4.1 (s)
Q1 2.34 2.06
Q2 0.14 0.22
Q3 0.72 1.50
Q4 0.56 0.46
Q5 2.25 0.95
Q6 0.23 0.13
Q7 1.52 1.48
Q8 0.70 0.61
Q9 5.22 2.95
Q10 1.24 1.02
Q11 0.23 0.18
Q12 1.62 1.13
Q13 2.41 1.95
Q14 0.36 0.28
Q15 0.79 0.88
Q16 0.66 0.62
Q17 0.63 0.54
Q18 0.93 0.83
Q19 0.78 0.61
Q20 1.17 1.09
Q21 2.42 2.63
Q22 1.24 1.09
Total 28.16 23.21

TPC-DS benchmark test

Test plan:

  1. Use OBD to deploy an OceanBase cluster. Deploy the client on a separate server for stress testing. You do not need to deploy ODP. You can connect to any server during testing.
  2. Deploy the OceanBase cluster in the 1-1-1 architecture, where the cluster has three zones and each zone has one OBServer node. After successful deployment, create the tenant and users required for running the TPC-DS benchmark. The sys tenant is a built-in system tenant for managing the cluster. Do not use the sys tenant to run the benchmark. Set primary_zone to RANDOM for the tenant. Load the data, sequentially execute 99 SQL queries, and take the average value.
  3. Size of the test dataset: 100 GB.

Tenant information:

  • MAX_CPU = 26
  • MEMORY_SIZE = 70 GB

Results:

Query
V4.1 (s)
Q1 0.63
Q2 3.46
Q3 0.16
Q4 9.43
Q5 1.63
Q6 0.37
Q7 0.28
Q8 0.39
Q9 1.89
Q10 0.50
Q11 5.79
Q12 0.28
Q13 2.04
Q14 11.38
Q15 0.23
Q16 0.92
Q17 0.52
Q18 0.32
Q19 0.17
Q20 0.19
Q21 0.29
Q22 1.11
Q23 14.20
Q24 1.56
Q25 0.62
Q26 0.21
Q27 0.35
Q28 7.44
Q29 0.64
Q30 0.27
Q31 0.62
Q32 0.11
Q33 0.77
Q34 0.37
Q35 0.87
Q36 0.31
Q37 0.42
Q38 1.49
Q39 2.31
Q40 0.16
Q41 0.18
Q42 0.11
Q43 0.64
Q44 0.45
Q45 0.39
Q46 0.81
Q47 1.16
Q48 0.61
Q49 0.86
Q50 0.81
Q51 2.82
Q52 0.11
Q53 0.24
Q54 1.05
Q55 0.11
Q56 1.01
Q57 0.79
Q58 0.60
Q59 13.64
Q60 1.13
Q61 0.30
Q62 0.40
Q63 0.23
Q64 1.84
Q65 2.70
Q66 0.46
Q67 16.12
Q68 0.67
Q69 0.44
Q70 1.18
Q71 0.54
Q72 1.47
Q73 0.31
Q74 6.36
Q75 2.26
Q76 0.49
Q77 0.49
Q78 3.64
Q79 0.65
Q80 1.78
Q81 0.30
Q82 0.67
Q83 0.69
Q84 0.19
Q85 0.84
Q86 0.36
Q87 1.59
Q88 0.65
Q89 0.30
Q90 0.19
Q91 0.13
Q92 0.10
Q93 0.75
Q94 0.62
Q95 6.37
Q96 0.38
Q97 0.93
Q98 0.30
Q99 0.70
Total time 160.83

Compatibility changes

Product behavioral changes

Feature
Version
Change description
Floating-point data types V4.1 V4.0: The float(m,d) format definition is no longer supported. Only float(m) and float(m,0) are supported.
V4.1: This version is fully compatible with the data types and precisions in MySQL 8.0.
Backup file name extension V4.1 The file name extension .obbak is added to identify backup files of OceanBase Database.
The file name extension .obarc is added to identify archived log files of OceanBase Database.
UNUSABLE index V4.1 UNUSABLE indexes that are generated after partitions are deleted cannot be restored from the backup.
MAJOR FREEZE V4.1 You can initiate a major compaction task for a specific tenant, tablet, or table.

Views, entity tables, and virtual tables

Views, entity tables, and virtual tables
Usage and incompatibility
New/Change
Version
__all_virtual_plan_table Stores the current session explain plan. New V4.1
__all_virtual_sql_plan Stores the executed logical plans. New V4.1
__all_virtual_ha_diagnose Displays the diagnostic information about the current garbage collection (GC) status, including gc_diagnose_info, restore_handler_role, restore_handler_proposal_id, restore_context_info, and restore_err_context_info. Change V4.1
__all_virtual_malloc_sample_info Displays the stack information about memory allocation for each module. New V4.1
__all_ddl_task_status The execution_id column is added to identify each single-replica building task. Change V4.1
__all_virtual_span_info Stores diagnostic information. New V4.1
__all_virtual_show_trace Displays the processed diagnostic information. New V4.1
__all_virtual_io_scheduler Displays the IOPS and bandwidth statistics. New V4.1
__all_virtual_io_status Displays the queuing status of different types of I/O requests for different tenants. New V4.1
V$OB_SQL_AUDIT The PARTITION_HIT field is added to indicate whether partition routing is remotely performed. Change V4.1
DBA_RSRC_PLAN_DIRECTIVES Displays the configuration of I/O resources in the resource manager. New V4.1
V$OB_TABLET_STATS Displays the tablet-level statistics on adaptive compactions, which are used in troubleshooting. New V4.1
DBA_OB_TENANTS Regular users are allowed to query this view and the following columns are added to display information such as the locality, synchronization timestamp, and tenant type: TENANT_ROLE, SWITCHOVER_STATUS, SWITCHOVER_EPOCH, SYNC_SCN, REPLAYABLE_SCN, READABLE_SCN, RECOVERY_UNTIL_SCN, LOG_MODE, and ARBITRATION_SERVICE_STATUS. Change V4.1
V$OB_LOG_STAT The arbitration_member and degraded_list columns are added to indicate the arbitration members and the list of degraded replicas. Change V4.1
V$OB_TRANSACTION_SCHEDULERS Displays the information about schedulers of transactions, which can be used for troubleshooting. New V4.1
DBA_OB_ARBITRATION_SERVICE Displays the arbitration service configuration information of the current cluster. New V4.1
DBA_OB_LS_ARB_REPLICA_TASKS Displays the running arbitration replica tasks of the current tenant and the corresponding user tenant. New V4.1
DBA_OB_LS_ARB_REPLICA_TASK_HISTORY Displays the executed arbitration replica tasks of the current tenant and the corresponding user tenant. New V4.1
V$OB_ARCHIVE_DEST_STATUS Displays the status of each archive destination of the tenant. New V4.1
DBA_OB_LS_LOG_ARCHIVE_PROGRESS Displays the archiving progress at the log stream level. New V4.1
DBA_OB_LS_LOG_RESTORE_STAT Displays the restoration summary at the log stream level. New V4.1
DBA_OB_CLUSTER_EVENT_HISTORY Displays only events related to cluster upgrades. This view is accessible only from the sys tenant. New V4.1
DBA_OB_TENANTS Displays the basic information of all tenants. Change V4.1

Parameter changes

Parameter
Usage and incompatibility
Status change
Version
ob_proxy_readonly_transaction_routing_policy The routing strategy for read-only statements. Deprecated. V4.1
ob_plan_table_memory_limit The maximum memory available for the optimizer to store logical plans. Default value: 32 MB. Value range: 1 to 1024. V4.1
tenant_task_queue_size The length of the request queue of the tenant. The default value is changed from 65536 to 8192. V4.1
ob_enable_trace_log Specifies whether to enable SQL Trace. Deprecated. V4.1
ob_enable_show_trace Specifies whether to enable Show Trace. Default value: 0, which specifies to disable Show Trace. V4.1
_data_storage_io_timeout The maximum I/O timeout period of the data disk. The default value is changed from 120s to 10s, and the minimum value is changed from 5s to 1s. V4.1
_enable_pkt_nio Specifies whether to enable PKT-NIO for the new remote procedure call (RPC) framework. Default value: True. V4.1
rpc_memory_limit_percentage The maximum memory for RPCs in the tenant. Default value: 0, which specifies not to limit the memory for RPCs. V4.1
_private_buffer_size The size of the log buffer that triggers log writing. The default value is changed from 256 KB to 16 KB. V4.1
_mvcc_gc_using_min_txn_snapshot Specifies whether to use active transaction snapshots to store multiversion data. Default value: True. V4.1
_ob_enable_dynamic_worker Specifies whether to enable dynamic threads. Default value: True. V4.1
data_storage_warning_tolerance_time The maximum duration of I/O failures tolerable on the data disk before the data disk is considered damaged. Default value: 5s. Value range: 1s to 300s. V4.1
log_storage_warning_tolerance_time The maximum duration of I/O failures tolerable on the log disk before the log disk is considered damaged. Default value: 5s. Value range: 1s to 300s. V4.1
_min_malloc_sample_interval The minimum sampling interval in memory allocation. Default value: 16. Value range: 1 to 10000. V4.1
_max_malloc_sample_interval The maximum sampling interval in memory allocation. Default value: 256. Value range: 1 to 10000. V4.1
ob_max_read_stale_time The session-level maximum latency in weak-consistency reads. For the weak-consistency read requests in the current session, the latency of the read data is within the specified threshold. You can set different latency thresholds for different sessions. Default value: 5s. V4.1
log_archive_concurrency The total number of worker threads for archiving logs. You can dynamically increase or decrease the number of threads. The effective scope of this parameter is changed from the cluster level to the tenant level. V4.1
log_restore_concurrency The number of worker threads for restoring logs from the physical database or standby database. You can dynamically increase or decrease the number of threads. The effective scope of this parameter is changed from the cluster level to the tenant level. V4.1
_ob_enable_direct_load Specifies whether to enable bypass import. Default value: True. V4.1
_enable_transaction_internal_routing Specifies whether DML statements executed within a transaction can be routed to any OBServer node. Default value: True. V4.1
log_restore_source The path from which logs are restored. Default value: "". V4.1
ob_startup_mode The startup mode of the observer process. Default value: normal. The value arbitration specifies to start the observer process in arbitration mode. V4.1
_ob_plan_cache_auto_flush_interval The interval for periodically flushing the plan cache. Default value: 0s, which specifies not to automatically flush the plan cache. V4.1
enable_user_defined_rewrite_rules Specifies whether to enable user-defined rules. Default value: False. V4.1

Note

  • An online upgrade from OceanBase Database V3.x to OceanBase Database V4.x is not supported.
  • You can use OMS to migrate the data logic of OceanBase Database V3.x to OceanBase Database V4.1.
  • An online upgrade from OceanBase Database V4.0 to OceanBase Database V4.1 is supported.

Supported components

The following table describes the recommended component versions for OceanBase Database V4.1.0.

Component
Version
ODP V4.1.0
OceanBase Connector/J V2.4.3
OceanBase Connector/ODBC V2.0.7
OceanBase Client (OBClient) V2.2.2
OBD V2.0.0
OceanBase Agent (OBAgent) V1.3.0
ob-operator V1.2.0
MySQL JDBC driver V5.1.47

Limitation

  • In OceanBase Database V4.1.0, load balancing is not supported after replica scale-out. Therefore, data that already exists before the scale-out cannot be distributed to the newly added nodes. This issue will be resolved in V4.2.
  • OceanBase Database V4.1.0 does not support replicated tables. This issue will be resolved in V4.2.
  • OceanBase Database V4.1.0 allows you to initiate data backup from the primary cluster. You will be able to initiate data backup from the standby cluster in later versions.
  • In OceanBase Database V4.1.0, the minimum specification of a node in the production environment is 4C16GB. Each tenant requires more than 2 GB of memory and more than 1 CPU core.
  • OceanBase Database V4.1.0 supports only full-featured replicas. Other types of replicas such as read-only replicas will be supported in later versions.
  • In OceanBase Database V4.1.0, you can only increase the number of resource units (UNIT_NUM) of a tenant. You will be allowed to decrease the number of resource units in later versions.
  • In OceanBase Database V4.1.0, if you execute the DROP DATABASE statement to drop more than 200 tables from a database at a time, the operation may fail. We recommend that you first execute DROP TABLE and then DROP DATABASE. This issue will be resolved in V4.2.

V4.1.0

Version information

  • Release date: April 20, 2023
  • Version: V4.1.0

Overview

This version fixes some bugs and improves stability.

Bug fixes

  • Fixed a backup failure issue which occurred when many empty tablets exist.
  • Fixed a bug where stack overflow would occur when the operating system page size is set to 64 KB.
  • Fixed a bug of failing to read the lob data length after the upgrade from version 4.0 to version 4.1.
  • Fixed a bug of memory leak caused by the ModulePageAlloc module.
  • Fixed a disconnection issue caused by the lack of updating session active time in the response logic of COM_PING.
  • Fixed the bug where the OUTPUT_BYTES statistics in the CDB_OB_BACKUP_SET_FILES view was not accurate.

Note

  • OBD V2.0.0 does not support the upgrade of OceanBase Database from V4.0.0 to V4.1.0.
  • OCP V4.0.3_CE now supports the upgrade of OceanBase Database from V4.0.0 to V4.1.0.

V4.1.0 BP1

Version information

  • Release date: May 12, 2023
  • Version: V4.1.0 BP1

Overview

This version fixes some bugs and improves stability.

Bug fixes

  • Fixed an issue where the error code of the REGEXP BINARY expression was incompatible with that of MySQL.
  • Fixed a bug where the SQL execution result sets were duplicated after IN expression optimization.
  • Fixed a bug where OceanBase Database deployed in a Kubernetes cluster failed to start due to too many virtual network cards.
  • Fixed a bug where the execution plan was not generated as expected after an index was created on a generated column and used for table access.
  • Fixed an issue that OceanBase Database does not support the NULLABLE field in the information_schema.STATISTICS view.
  • Fixed a bug where plan cache eviction would fail if an SQL execution plan occupies too much memory and contains expressions that cannot be parameterized.
  • Fixed a bug related to encoding data estimation error, which resulted in the writing of more than 2 MB of encoded data into the macroblock memory buffer. This bug would result in macroblock serialization failure, which in turn caused the major compaction to be stuck.

Note

OBD V2.1.0 and later support the upgrade of OceanBase Database from V4.0.0 to V4.1.0.

次のトピック

OceanBaseデータベース Community版 V4.4.2
次へ
このページの内容
V4.1.0 Beta
Version information
Overview
Features
Performance report
Compatibility changes
Note
Supported components
Limitation
V4.1.0
Version information
Overview
Bug fixes
Note
V4.1.0 BP1
Version information
Overview
Bug fixes
Note