VLDB 2023 - OceanBase Paetica- A Hybrid Shared-nothing_Shared-everything Database for Supporting Single Machine and Distributed Cluster.pdf

章芋文

638

13页

31次

2023-08-31

免费下载

OceanBase Paetica: A Hybrid Shared-nothing/Shared-ever ything

Database for Supporting Single Machine and Distributed Cluster

Zhifeng Yang

∗

OceanBase, Ant Group

Quanqing Xu

∗

OceanBase, Ant Group

Shanyan Gao

OceanBase, Ant Group

Chuanhui Yang

†

OceanBase, Ant Group

Guoping Wang

OceanBase, Ant Group

Yuzhong Zhao

OceanBase, Ant Group

Fanyu Kong

OceanBase, Ant Group

Hao Liu

OceanBase, Ant Group

Wanhong Wang

OceanBase, Ant Group

Jinliang Xiao

OceanBase, Ant Group

OceanBaseLabs@service.oceanbase.com

ABSTRACT

In the ongoing evolution of the OceanBase database system, it

is essential to enhance its adaptability to small-scale enterprises.

The OceanBase database system has demonstrated its stability and

eectiveness within the Ant Group and other commercial orga-

nizations, besides through the TPC-C and TPC-H tests. In this

paper, we have designed a stand-alone and distributed integrated

architecture named Paetica to address the overhead caused by the

distributed components in the stand-alone mode, with respect to the

OceanBase system. Paetica enables adaptive conguration of the

database that allows OceanBase to support both serial and parallel

executions in stand-alone and distributed scenarios, thus provid-

ing eciency and economy. This design has been implemented in

version 4.0 of the OceanBase system, and the experiments show

that Paetica exhibits notable scalability and outperforms alternative

stand-alone or distributed databases. Furthermore, it enables the

transition of OceanBase from primarily serving large enterprises

to truly catering to small and medium enterprises, by employing a

single OceanBase database for the successive stages of enterprise or

business development, without the requirement for migration. Our

experiments conrm that Paetica has achieved linear scalability

with the increasing CPU core number within the stand-alone mode.

It also outperforms MySQL and Greenplum in the Sysbench and

TPC-H evaluations.

PVLDB Reference Format:

Zhifeng Yang, Quanqing Xu, Shanyan Gao, Chuanhui Yang, Guoping

Wang, Yuzhong Zhao, Fanyu Kong, Hao Liu, Wanhong Wang, and Jinliang

Xiao. OceanBase Paetica: A Hybrid Shared-nothing/Shared-everything

Database for Supporting Single Machine and Distributed Cluster. PVLDB,

16(12): 3728 - 3740, 2023.

doi:10.14778/3611540.3611560

∗

These authors contributed equally to this work.

†

Chuanhui Yang is the corresponding author.

This work is licensed under the Creative Commons BY-NC-ND 4.0 International

License. Visit https://creativecommons.org/licenses/by-nc-nd/4.0/ to view a copy of

this license. For any use beyond those covered by this license, obtain permission by

emailing info@vldb.org. Copyright is held by the owner/author(s). Publication rights

licensed to the VLDB Endowment.

Proceedings of the VLDB Endowment, Vol. 16, No. 12 ISSN 2150-8097.

doi:10.14778/3611540.3611560

PVLDB Artifact Availability:

The source code, data, and/or other artifacts have been made available at

https://github.com/oceanbase/obdeploy.

1 INTRODUCTION

Initially, we have designed and developed the OceanBase system in

version 0.5, which utilizes a divided storage and computing layer,

thus resulting in signicant scalability. For further improvement

of the performance, we have then implemented version 3.0 of the

system, which features enhancements that enable higher through-

put and lower write latency, thus being capable of supporting the

various business operations within the Ant Group and other com-

mercial organizations. Furthermore, we made the system available

as open-source, and shared the design and technology of the sys-

tem within the open-source community. We have commercialized

OceanBase, for applying its technology and capabilities to the busi-

nesses of numerous large, medium, and small enterprises since

2017. It is worth noting that OceanBase was the only distributed

database that passed the TPC-C benchmark in 2020. However, the

version 3.0 of OceanBase was not that well-suited to medium and

small enterprises, probably owing to the overhead incurred by the

log streams and partition bounds in small-scale machines, besides

the additional overhead resulting from the interaction among the

distributed components during the deployment.

The emergence of distributed databases has resolved the issue

of horizontal scalability, but the stand-alone performance and SQL

functionality are signicantly inferior when compared to central-

ized databases, e.g., Oracle [

], MySQL [

], and PostgreSQL [

Many distributed databases have emerged during this process, and

some of them are distributed storage systems that only support

simple NoSQL functionality or limited SQL functionality, such as

Amazon Dynamo [19]. Furthermore, certain distributed databases

support both horizontal scalability and complete SQL functionality,

often referred to as NewSQL, such as CockroachDB [

] and Google

Spanner [

]. Citus [

] is an open source distributed PostgreSQL

for data-intensive applications through the PostgreSQL extension

APIs. However, their single-node performance is less than one-third

of that of MySQL.

Therefore, the choice between the stand-alone and distributed

system has become strenuous. Thus the typical decision-making is

3728

based on the data volume; i.e., if the data volume is relatively small, a

centralized database with complete functionality is chosen. Further,

if the data volume is huge, a distributed database or distributed

storage system is selected, thus sacricing the functionality and

stand-alone performance in order to address the issue by modifying

the business or adding machines.

We further enhanced OceanBase [

] to version 4.0, expecting

that it would better support small-scale enterprises. The system

integrates several storage shards with a shared log stream and

provides a high-availability service. Owing to the advancement

in technology, contemporary machines have come to feature mul-

tiple cores, large amounts of DRAM, and high-speed storage de-

vices. This highlights the importance of considering both horizontal

and vertical scalability in the design of a distributed database sys-

tem. Accordingly, we have developed Paetica

as a hybrid shared-

nothing/shared-everything cloud database system capable of sup-

porting both stand-alone and distributed integrated architecture.

We will describe the concept of Paetica in detail with the following

contributions.

•

We propose Paetica, a stand-alone and distributed inte-

grated architecture that is implemented in version 4.0 of

the OceanBase system. Paetica features independent SQL,

transaction, and storage engines in both the stand-alone

and distributed systems, which enables the dynamic cong-

uration switching by the user. The integrated architecture

design allows OceanBase to operate eciently without in-

curring the distributed interaction overhead in the stand-

alone mode. Furthermore, while operating in the distributed

mode, the system achieves high performance besides pro-

viding disaster tolerance.

•

We have developed a stand-alone and distributed integrated

SQL engine that is capable of processing SQL in diverse

situations. The engine has been designed to execute SQL

both in the serial and parallel manner to fully utilize the

available CPU cores. Furthermore, in distributed execu-

tion scenarios, the engine is capable of parallelism across

multiple machines that allows ecient processing of SQL

commands.

•

We have constructed a stand-alone and distributed inte-

grated LSM-Tree storage engine that includes various com-

paction optimizations for both the stand-alone and dis-

tributed modes. These optimizations include the techniques

such as incremental major compaction and staggered round-

robin compaction, which intends to achieve a balance be-

tween the write performance and storage space utilization.

•

For the stand-alone and distributed integrated transaction

processing engine, we have proposed an optimized version

of the 2-Phase Commit (2PC) protocol. This optimization

intends to reduce the message processing and log volume,

and subsequently decrease transaction latency. In the stand-

alone mode, Paetica does not require the use of 2PC and

instead utilizes a single log stream to process transactions

without accessing the global time service (GTS). Conse-

quently, the eciency of the transaction engine is compa-

rable to that of a stand-alone database.

Paetica is OceanBase version 4.0.

We have conducted scalability experiments to demonstrate the

linear scalability of Paetica. Our OLTP (Online Transaction Pro-

cessing) experiments also demonstrate that Paetica exhibits high

concurrency and low latency in both stand-alone and distributed

modes. We have also compared OceanBase 4.0 with MySQL 8.0 in a

separate experiment and found that OceanBase 4.0 performs better

than MySQL 8.0 in small-scale and stand-alone situations. Further-

more, we have compared Paetica with OceanBase version 3.1 and

Greenplum [

] 6.22.1 on the TPC-H [

] 100GB experiments, and it

is observed that Paetica outperforms OceanBase 3.1 5x on average.

Compared with Greenplum 6.22.1, Paetica demonstrates a superior

performance across all queries.

The paper is organized as follows. §2 presents the OceanBase

evolution. §3 provides an overview of the stand-alone and dis-

tributed architecture. §4 and §5 describe the integrated engine of

SQL and transaction processing. We present the experiments in §6

to prove the ecacy and economy of Paetica. We present discussion

including polymorphisim, dynamism and native multi-tenancy in

§7, and we review the related work in §8. Finally, we give the con-

clusions in §9. OceanBase is an open-source project under Mulan

Public License 2.0 [

] and the source code referenced in this paper

is available on both gitee [3] and GitHub [4].

2 OCEANBASE EVOLUTION

In this section, we illustrate the evolution of OceanBase from ver-

sion 0.5 to version 4.0.

2.1 OceanBase 0.5

OceanBase [

] has been developed since 2010. Figure 1 is the over-

all architecture diagram of OceanBase version 0.5. Concomitantly,

OceanBase has been divided into two layers, viz., storage and com-

puting. The upper layer is a service layer that provides SQL services

statelessly, and the lower layer is a storage cluster composed of two

kinds of servers: ChunkServer and UpdateServer. The ChunkServer

is characterized by the capability for automatic partitioning and

horizontal scalability of storage. The UpdateServer utilizes the Paxos

protocol [

] to attain strong consistency and availability. However,

the UpdateServer does not possess the capability for distributed

transactions. Such an architecture can enable OceanBase to bet-

ter support businesses similar to Taobao favorites [

]. Further, it

has certain scalability, particularly a relatively strong scalability of

reading, and the SQL layer is stateless and can be scaled freely.

Despite the advantages of this architecture, a major issue is that

the UpdateServer node is a single-point write, multi-point read archi-

tecture, which is similar to PolarDB [

][

] and makes it dicult

to expand when higher levels of concurrency become necessary.

Furthermore, according to Figure 1, splitting the storage and SQL

layers results in a high query delay. It is dicult to control the net-

work jitter, and controlling the jitter of latency can be challenging

under conditions of extremely high latency requirements.

2.2 OceanBase 1.0 ~ 3.0

To address the aforementioned issues, OceanBase has abandoned

its previous architecture and developed the version 1.0 ~ 3.0, which

is characterized by a fully peer-to-peer (P2P) structure as shown

Figure 2. Each OBServer contains SQL, storage, and transaction

3729

of 13

免费下载

关注

评论