删除原有的 downloads 目录 /home/tidb/tidb-ansible/downloads/ 1. $ cd /home/tidb/tidb-ansible 2. $ rm -rf downloads 3. 使用 playbook 下载 TiDB v2.0.3 版本 binary，自动替换 binary 到 /home/tidb/tidb- ansible/resource/bin/

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. 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

离线镜像合并后，执行下列命令升级 Cluster 组件： tiup update cluster 此时离线镜像已经更新成功。如果覆盖后发现 TiUP 运行报错，可能是 manifest 未更新导致，可尝试 rm -rf �→ ~/.tiup/manifests/* 后再使用。 8.1.1.2.3 2.3 编辑 TiUP Cluster 拓扑配置文件 注意： 以下情况可跳过此步骤： • 原集群没有修改过配置参数，或通过 key=${access-key}&secret-access-key=${secret-access-key}' 4. 清理该快照备份 FULL_BACKUP_TS 之前的快照备份数据。 rm -rf s3://backup-101/snapshot-${date} 8.3.3.3.4 PITR 的性能指标 • PITR 恢复速度，平均到单台 TiKV 节点：全量恢复为 280 GB/h，日志恢复为 Table 的计算量。 2. Build RF values +-------->+-------------------+ | |PhysicalHashJoin |<-----+ | +----+ | | 4. After RF | | +-------------------+ | 1. Scan T2 1306 5000 | |3. Send RF | 365 | | filter

离线镜像合并后，执行下列命令升级 Cluster 组件： tiup update cluster 此时离线镜像已经更新成功。如果覆盖后发现 TiUP 运行报错，可能是 manifest 未更新导致，可尝试 rm -rf �→ ~/.tiup/manifests/* 后再使用。 8.1.1.2.3 2.3 编辑 TiUP Cluster 拓扑配置文件 注意： 以下情况可跳过此步骤： • 原集群没有修改过配置参数，或通过 key=${access-key}&secret-access-key=${secret-access-key}' 4. 清理该快照备份 FULL_BACKUP_TS 之前的快照备份数据。 rm -rf s3://backup-101/snapshot-${date} 8.3.3.3.4 PITR 的性能指标 • PITR 恢复速度，平均到单台 TiKV 节点：全量恢复为 280 GB/h，日志恢复为 Table 的计算量。 2. Build RF values +-------->+-------------------+ | |PhysicalHashJoin |<-----+ | +----+ | | 4. After RF | | +-------------------+ | 1. Scan T2 5000 | |3. Send RF | 365 | | filter data

离线镜像合并后，执行下列命令升级 Cluster 组件： tiup update cluster 此时离线镜像已经更新成功。如果覆盖后发现 TiUP 运行报错，可能是 manifest 未更新导致，可尝试 rm -rf �→ ~/.tiup/manifests/* 后再使用。 8.1.1.2.3 2.3 编辑 TiUP Cluster 拓扑配置文件 注意： 以下情况可跳过此步骤： • 原集群没有修改过配置参数，或通过 key=${access-key}&secret-access-key=${secret-access-key}' 4. 清理该快照备份 FULL_BACKUP_TS 之前的快照备份数据。 rm -rf s3://backup-101/snapshot-${date} 8.3.3.3.4 PITR 的性能指标 • PITR 恢复速度，平均到单台 TiKV 节点：全量恢复为 280 GB/h，日志恢复为 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