2021/07/03 基于 TiDB 的云原生数据库实践 演讲人：王天宜 PingCAP 云 原 生 社 区 M e e t u p 第 四 期 成 都 站 目录 为什么云原生数据库要拥抱 Kubernetes 什么是云原生数据库 TiDB 在 AWS 上的最佳实践 1 CONTENTS 2 3 一、什么是云原生数据库 什么是云原生 2021/07/03 Cloud 2021/07/03 频繁发布 快速交付 快速反馈 降低发布风险 开发、测试、生产环境高度统 一 自动化部署管道、CI 工具 快速部署到生产环境 开发、运维协同工作 应用通过 rest API 通信 可以被独立部署、更新、 scale 和重启 什么是云原生数据库 2021/07/03 二、为何拥抱 Kubernetes Kubernetes 发展史 2021/07/03 Kubernetes 2021/07/03 初探 Database × Kubernetes 2021/07/03 初探 Database × Kubernetes 2021/07/03 TiDB 要以什么样的姿态拥抱 Kubernetes 2021/07/03 TiDB 要以什么样的姿态拥抱 Kubernetes 2021/07/03 TiDB 要以什么样的姿态拥抱

the state of 07:16, you can first restore the full backup (taken at 00:00) and the incremental backup (taken at 06:00), and then restore TiCDC logs that fill in the gap between 06:00 and 07:16. To peform ------------+---------------------+--------------+-----------+ �→ | test | t | | 2022-08-26 15:52:07 | 3 | �→ 6 | +-- �→ -------+------------+----------------+---------------------+--------------+-----------+ *************************** 1. row *************************** ID: 426831815660273668 START_TIME: 2021-08-06 07:16:00.081000 CURRENT_SQL_DIGEST: 06 �→ da614b93e62713bd282d4685fc5b88d688337f36e88fe55871726ce0eb80d7

the state of 07:16, you can first restore the full backup (taken at 00:00) and the incremental backup (taken at 06:00), and then restore TiCDC logs that fill in the gap between 06:00 and 07:16. To peform *************************** 1. row *************************** ID: 426831815660273668 START_TIME: 2021-08-06 07:16:00.081000 CURRENT_SQL_DIGEST: 06 �→ da614b93e62713bd282d4685fc5b88d688337f36e88fe55871726ce0eb80d7 update `t` set `v` = `v` + ? where `id` = ? ; STATE: LockWaiting 478 WAITING_START_TIME: 2021-08-06 07:16:00.087720 MEM_BUFFER_KEYS: 0 MEM_BUFFER_BYTES: 0 SESSION_ID: 77 USER: root DB: test ALL_SQL_DIGESTS:

------------+---------------------+--------------+-----------+ �→ | test | t | | 2022-08-26 15:52:07 | 3 | �→ 6 | +-- �→ -------+------------+----------------+---------------------+--------------+-----------+ *************************** 1. row *************************** ID: 426831815660273668 START_TIME: 2021-08-06 07:16:00.081000 CURRENT_SQL_DIGEST: 06 �→ da614b93e62713bd282d4685fc5b88d688337f36e88fe55871726ce0eb80d7 update `t` set `v` = `v` + ? where `id` = ? ; STATE: LockWaiting WAITING_START_TIME: 2021-08-06 07:16:00.087720 MEM_BUFFER_KEYS: 0 587 MEM_BUFFER_BYTES: 0 SESSION_ID: 77 USER: root DB: test ALL_SQL_DIGESTS:

data:Selection_6 �→ | | ￿─ Selection_6 | 0.80 | cop[tikv] | | ge(cast(findpt.t1 �→ .a), 1.2123123e+07), le(cast(findpt.t1.a), 1.1112222111111112e+21) | | ￿─ TableFullScan_5 | 1.00 | cop[tikv] | table:t1 v6.1.0, v6.1.1, and v6.1.2: 1.18 or later For TiDB v6.1.3: 1.19.3 or later | | Rust | nightly-2022-07-31 or later | | GCC | 7.x | | LLVM | 13.0 or later | Library required for running TiDB: glibc (2.28-151 snapshot generated at 2022-01-30 07:42:23 to the 2022-01-30/ directory in the backup-data bucket of Amazon S3. br backup full \ --pd "${PDIP}:2379" \ --backupts '2022-01-30 07:42:23' \ --storage "s3://ba

the state of 07:16, you can first restore the full backup (taken at 00:00) and the incremental backup (taken at 06:00), and then restore TiCDC logs that fill in the gap between 06:00 and 07:16. To peform START_TIME: 2021-06-08 08:46:48.341000 CURRENT_SQL_DIGEST: �→ a4e28cc182bdd18288e2a34180499b9404cd0ba07e3cc34b6b3be7b7c2de7fe9 STATE: LockWaiting WAITING_START_TIME: 2021-06-08 08:46:48.388024 MEM_BUFFER_KEYS: 7847bee4cfc8f3cdf3, �→ a4e28cc182bdd18288e2a34180499b9404cd0 ba07e3cc34b6b3be7b7c2de7fe9, �→ a4e28cc182bdd18288e2a34180499b9404cd0ba07e3cc34b6b3be7b7c2de7fe9] *************************** 2. row ***

*************************** 1. row *************************** ID: 426831815660273668 START_TIME: 2021-08-06 07:16:00.081000 CURRENT_SQL_DIGEST: 06da614b93e62713bd282d4685fc5b88d688337f36e88fe55871726ce0eb80d7 update `t` set `v` = `v` + ? where `id` = ? ; STATE: LockWaiting WAITING_START_TIME: 2021-08-06 07:16:00.087720 MEM_BUFFER_KEYS: 0 MEM_BUFFER_BYTES: 0 SESSION_ID: 77 USER: root DB: test ALL_SQL_DIGESTS: *************************** 2. row *************************** ID: 426831818019569665 START_TIME: 2021-08-06 07:16:09.081000 CURRENT_SQL_DIGEST: 06da614b93e62713bd282d4685fc5b88d688337f36e88fe55871726ce0eb80d7

Guide ● PID: the PID of the TiDB process Example: [2019/07/24 22:13:30.099 +08:00] [INFO] [logger.go:71] [ID="15640224010"] [TIMESTAMP=2019/07/24 22:13:30.099 +08:00] [EVENT_CLASS=CONNECTION] [EVENT type ● PID: the PID of the TiDB process Example: [2019/07/24 22:35:01.640 +08:00] [INFO] [logger.go:71] [ID="15640226010"] [TIMESTAMP=2019/07/24 22:35:01.640 +08:00] [EVENT_CLASS=TABLE_ACCESS] [EVENT_SUBCLASS=Insert] 14 TiDB Audit Plugin User Guide [2019/07/24 22:31:22.612 +08:00] [INFO] [logger.go:71] [ID="15640334010"] [TIMESTAMP=2019/07/24 22:31:22.612 +08:00] [EVENT_CLASS=GENERAL] [EVENT_SUBCLASS=]

---------------+---------------------+--------------+-----------+ | test | t | | 2022-08-26 15:52:07 | 3 | 6 | +---------+------------+----------------+---------------------+--------------+-----------+ *************************** 1. row *************************** ID: 426831815660273668 START_TIME: 2021-08-06 07:16:00.081000 CURRENT_SQL_DIGEST: 06da614b93e62713bd282d4685fc5b88d688337f36e88fe55871726ce0eb80d7 update `t` set `v` = `v` + ? where `id` = ? ; STATE: LockWaiting WAITING_START_TIME: 2021-08-06 07:16:00.087720 MEM_BUFFER_KEYS: 0 MEM_BUFFER_BYTES: 0 SESSION_ID: 77 USER: root DB: test ALL_SQL_DIGESTS:

data:Selection_6 �→ | | ￿─ Selection_6 | 0.80 | cop[tikv] | | ge(cast(findpt.t1 �→ .a), 1.2123123e+07), le(cast(findpt.t1.a), 1.1112222111111112e+21) | | ￿─ TableFullScan_5 | 1.00 | cop[tikv] | table:t1 Libraries required for compiling and building TiDB Version Golang 1.19 or later Rust nightly-2022-07-31 or later GCC 7.x LLVM 13.0 or later Library required for running TiDB: glibc (2.28-151.el8 version） status: ￿ NORMAL start: 2022-07-14 20:08:03.268 +0800 end: 2090-11-18 22:07:45.624 +0800 storage: s3://backup-101/logbackup speed(est.): 0.82 ops/s checkpoint[global]: 2022-07-25 22:52:15.518 +0800; gap=2m52s