Open Source Conference 2022 Online/Spring RDBMSとNoSQLのメリットを併せ持つクラウドネイティブなNewSQLデータベース 「TiDB」をKubernetesで動かしてみよう！ Executive Technical Advisor / Makoto Hasegawa 2 Makoto Hasegawa Working at // PingCAP(JP) NewSQL製品「TiDB」を主に開発 ワールドワイドにビジネスを展開中 (1600社以上の採用実績) CNCF に「TiKV」及び「Chaos Mesh」を寄与 Open Source Conference 2022 Online/Spring 5 TiKV は CNCF で「Graduated」プロジェクトと認定されています Chaos Mesh は現在「Incubating」ステータスとなっています Open Conference 2022 Online/Spring 6 2021年4月に日本法人が発足しました ??? Open Source Conference 2022 Online/Spring 7 ? 本日のアジェンダ? TiDB について理解しよう Kubernetes で TiDB を構築する際のポイント Kubernetes で TiDB を運用する際のポイント まとめ Open Source

TiUP operation after the overwriting, it might be that the manifest is not updated. You can try rm -rf ~/.tiup/manifests/* before running TiUP again. 837 8.1.1.2.3 Step 3: Edit TiUP topology configuration secret-access-key}' 4. Delete snapshot data earlier than the snapshot backup FULL_BACKUP_TS: rm -rf s3://backup-101/snapshot-${date} 8.3.3.3.4 Performance capabilities of PITR • On each TiKV node, hash table. 2. Build RF values +-------->+-------------------+ | |PhysicalHashJoin |<-----+ | +----+ | | 4. After RF | | +-------------------+ | 1. Scan T2 5000 | |3. Send RF | 365 | | filter data

TiUP operation after the overwriting, it might be that the manifest is not updated. You can try rm -rf ~/.tiup/manifests/* before running TiUP again. 856 8.1.1.2.3 Step 3: Edit TiUP topology configuration secret-access-key}' 4. Delete snapshot data earlier than the snapshot backup FULL_BACKUP_TS: rm -rf s3://backup-101/snapshot-${date} 8.3.3.3.4 Performance capabilities of PITR • On each TiKV node, hash table. 2. Build RF values +-------->+-------------------+ | |PhysicalHashJoin |<-----+ | +----+ | | 4. After RF | | +-------------------+ | 1. Scan T2 5000 | |3. Send RF | 365 | | filter data

TiUP operation after the overwriting, it might be that the manifest is not updated. You can try rm -rf ~/.tiup/manifests/* before running TiUP again. 828 8.1.1.2.3 Step 3: Edit TiUP topology configuration hash table. 2. Build RF values +-------->+-------------------+ | |PhysicalHashJoin |<-----+ | +----+ | | 4. After RF | | +-------------------+ | 1. Scan T2 5000 | |3. Send RF | 365 | | filter data TableFullScan | | TableFullScan | | store_sales | | date_dim | +-----------------+ +----------------+ (RF is short for Runtime Filter) From the above two figures, you can see that the amount of data scanned

TiUP operation after the overwriting, it might be that the manifest is not updated. You can try rm -rf ~/.tiup/manifests/* before running TiUP again. 8.2.1.2.3 Step 3: Edit TiUP topology configuration hash table. 2. Build RF values +-------->+-------------------+ | |PhysicalHashJoin |<-----+ | +----+ | | 4. After RF | | +-------------------+ | 1. Scan T2 5000 | |3. Send RF | 365 | | filter data TableFullScan | | TableFullScan | | store_sales | | date_dim | +-----------------+ +----------------+ (RF is short for Runtime Filter) From the above two figures, you can see that the amount of data scanned

TiUP operation after the overwriting, it might be that the manifest is not updated. You can try rm -rf ~/.tiup/manifests/* before running TiUP again. 8.2.1.2.3 Step 3: Edit TiUP topology configuration hash table. 2. Build RF values +-------->+-------------------+ | |PhysicalHashJoin |<-----+ | +----+ | | 4. After RF | | +-------------------+ | 1. Scan T2 5000 | |3. Send RF | 365 | | filter data TableFullScan | | TableFullScan | | store_sales | | date_dim | +-----------------+ +----------------+ (RF is short for Runtime Filter) From the above two figures, you can see that the amount of data scanned

TiUP operation after the overwriting, it might be that the manifest is not updated. You can try rm -rf ~/.tiup/manifests/* before running TiUP again. 879 8.2.1.2.3 Step 3: Edit TiUP topology configuration hash table. 2. Build RF values +-------->+-------------------+ | |PhysicalHashJoin |<-----+ | +----+ | | 4. After RF | | +-------------------+ | 1. Scan T2 5000 | |3. Send RF | 365 | | filter data TableFullScan | | TableFullScan | | store_sales | | date_dim | +-----------------+ +----------------+ (RF is short for Runtime Filter) From the above two figures, you can see that the amount of data scanned

TiUP operation after the overwriting, it might be that the manifest is not updated. You can try rm -rf ~/.tiup/manifests/* before running TiUP again. 8.2.1.2.3 Step 3: Edit TiUP topology configuration hash table. 2. Build RF values +-------->+-------------------+ | |PhysicalHashJoin |<-----+ | +----+ | | 4. After RF | | +-------------------+ | 1. Scan T2 5000 | |3. Send RF | 365 | | filter data TableFullScan | | TableFullScan | | store_sales | | date_dim | +-----------------+ +----------------+ (RF is short for Runtime Filter) From the above two figures, you can see that the amount of data scanned

TiUP operation after the overwriting, it might be that the manifest is not updated. You can try rm -rf ~/.tiup/manifests/* before running TiUP again. 8.2.1.2.3 Step 3: Edit TiUP topology configuration hash table. 2. Build RF values +-------->+-------------------+ | |PhysicalHashJoin |<-----+ | +----+ | | 4. After RF | | +-------------------+ | 1. Scan T2 5000 | |3. Send RF | 365 | | filter data TableFullScan | | TableFullScan | | store_sales | | date_dim | +-----------------+ +----------------+ 1708 (RF is short for Runtime Filter) From the above two figures, you can see that the amount of data scanned

"Table Name", (SELECT MAX(I.RDB$STATISTICS) || ' (' || COUNT(*) || ')' FROM RDB$RELATION_FIELDS RF WHERE RF.RDB$RELATION_NAME = 121 Руководство по языку SQL R.RDB$RELATION_NAME ) AS "Max. IndexSel RDB$RELATION_NAME TABLE_NAME, SUM( (SELECT COUNT(*) FROM RDB$RELATION_FIELDS RF WHERE 123 Руководство по языку SQL RF.RDB$RELATION_NAME = R.RDB$RELATION_NAME ) ) AS IND_X_FIELDS FROM RDB$RELATIONS AS FIELDCOUNT 129 Руководство по языку SQL FROM RDB$RELATIONS R JOIN RDB$RELATION_FIELDS RF ON RF.RDB$RELATION_NAME = R.RDB$RELATION_NAME GROUP BY RELATION) GROUP BY FIELDCOUNT Тривиальный пример