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 要以什么样的姿态拥抱

>: CreateKeyspace -keyspace_type=SNAPSHOT -base_keyspace=originalks -snapshot_time=2020-07-17T18:25:20Z restoreks Here: • originalks is the base keyspace, i.e. the keyspace we took a backup charset=utf-8 W0817 07:20:08.822742 7735 main.go:64] W0817 14:20:08.821985 reparent.go:185] master -elect tablet zone1 -0000000100 is not the shard master, proceeding anyway as -force was used W0817 07:20:08.823004 proceeding anyway as -force was used I0817 07:20:08.823239 7735 main.go:64] I0817 14:20:08.823075 reparent.go:222] resetting replication on tablet zone1 -0000000100 I0817 07:20:08.833215 7735 main.go:64] I0817

p2 VALUES VALUES [[(("2014-06-01" "2014-06-01",, "100" "100",, "200" "200")),, (("2014-07-01" "2014-07-01",, "100" "100",, "300" "300")))) )) DISTRIBUTED DISTRIBUTED BY BY HASH HASH((k2 k2)) CreateTime: 2019 2019--07 07--27 27 11 11::46 46::42 42 EtlStartTime: EtlStartTime: 2019 2019--07 07--27 27 11 11::46 46::44 44 EtlFinishTime: EtlFinishTime: 2019 2019--07 07--27 27 11 11::46 46::44 46::44 44 LoadStartTime: LoadStartTime: 2019 2019--07 07--27 27 11 11::46 46::44 44 LoadFinishTime: LoadFinishTime: 2019 2019--07 07--27 27 11 11::50 50::16 16 URL: http:

>: CreateKeyspace -keyspace_type=SNAPSHOT -base_keyspace=originalks -snapshot_time=2020-07-17T18:25:20Z restoreks Here: - originalks is the base keyspace, i.e. the keyspace we took a backup charset=utf-8 W0817 07:20:08.822742 7735 main.go:64] W0817 14:20:08.821985 reparent.go:185] master -elect tablet zone1 -0000000100 is not the shard master, proceeding anyway as -force was used W0817 07:20:08.823004 proceeding anyway as -force was used I0817 07:20:08.823239 7735 main.go:64] I0817 14:20:08.823075 reparent.go:222] resetting replication on tablet zone1 -0000000100 I0817 07:20:08.833215 7735 main.go:64] I0817

>: CreateKeyspace -keyspace_type=SNAPSHOT -base_keyspace=originalks -snapshot_time=2020-07-17T18:25:20Z restoreks Here: • originalks is the base keyspace, i.e. the keyspace we took a backup W0817 07:20:08.822742 7735 main.go:64] W0817 14:20:08.821985 reparent.go:185] primary -elect tablet zone1 -0000000100 is not the shard primary , proceeding anyway as -force was used 347 W0817 07:20:08 proceeding anyway as -force was used I0817 07:20:08.823239 7735 main.go:64] I0817 14:20:08.823075 reparent.go:222] resetting replication on tablet zone1 -0000000100 I0817 07:20:08.833215 7735 main.go:64] I0817

>: CreateKeyspace -keyspace_type=SNAPSHOT -base_keyspace=originalks -snapshot_time=2020-07-17T18:25:20Z restoreks Here: - originalks is the base keyspace, i.e. the keyspace we took a backup charset=utf-8 W0817 07:20:08.822742 7735 main.go:64] W0817 14:20:08.821985 reparent.go:185] master -elect tablet zone1 -0000000100 is not the shard master, proceeding anyway as -force was used W0817 07:20:08.823004 proceeding anyway as -force was used I0817 07:20:08.823239 7735 main.go:64] I0817 14:20:08.823075 reparent.go:222] resetting replication on tablet zone1 -0000000100 I0817 07:20:08.833215 7735 main.go:64] I0817

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 10. Index B-Tree Page — Type 0x07 — YOU ARE HERE.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Inventory Pages or TIP (page type 0x03), Pointer Pages (page type 0x04), Index BTree Pages (page type 0x07), Data Pages (page type 0x05) and so on. There is a discussion of each page type below. 2.2. Multiple Header 5 0x06 Index Root Page. Similar to a type 4 Pointer Page, but applies to indexes only. 0x07 Index B-Tree Page. Similar to the type 5 Data Page, but applies to indexes only. 0x08 Blob Page. Blobs

>: CreateKeyspace -keyspace_type=SNAPSHOT -base_keyspace=originalks -snapshot_time=2020-07-17T18:25:20Z restoreks Here: - originalks is the base keyspace, i.e. the keyspace we took a backup charset=utf-8 W0817 07:20:08.822742 7735 main.go:64] W0817 14:20:08.821985 reparent.go:185] master -elect tablet zone1 -0000000100 is not the shard master, proceeding anyway as -force was used W0817 07:20:08.823004 proceeding anyway as -force was used I0817 07:20:08.823239 7735 main.go:64] I0817 14:20:08.823075 reparent.go:222] resetting replication on tablet zone1 -0000000100 I0817 07:20:08.833215 7735 main.go:64] I0817

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: