【 TiDB 使用环境】生产环境
【 TiDB 版本】
【复现路径】备份可复现
【遇到的问题：问题现象及影响】
使用 br进行备份,但是备份最后的大小只有 376 B,这个正好是 metadata 文件的大小,云厂商遍历日志,看 get 请求获取了这个文件的大小,是不是这块代码有变动,导致获取的备份大小不正确呢,看 br 的备份日志,上传压缩有正常的文件大小,但是在请求的时候返回的就是 376B
I0829 04:36:14.817759 9 backup.go:302] [2024/08/29 04:36:14.817 +00:00] [INFO] [collector.go:264] [“Database Backup success summary”] [total-ranges=2416] [ranges-succeed=2416] [ranges-failed=0] [backup-checksum=16.486915386s] [backup-fast-checksum=131.463702ms] [backup-total-ranges=3737] [total-take=3m13.143479175s] [BackupTS=452173754081738758] [total-kv=289501843] [total-kv-size=110.9GB] [average-speed=574.3MB/s] [backup-data-size(after-compressed)=19.7GB] [Size=19702953781]
I0829 04:36:14.835232 9 backup.go:302]
I0829 04:36:14.835551 9 backup.go:322] Run br commond [backup db --pd=tidb-tianji-new-pd.tidb-tianji-new:2379 --send-credentials-to-tikv=true --storage=s3://xxx-tidb-backup-s3/TiDB-tianji-new/xxx_db/offline/202408291230 --s3.region=bj --s3.provider=other --s3.endpoint=https://s3.bj.bcebos.com --db=xxx_db --ratelimit=500] for cluster tidb-tianji-new/tianjing-db-backup-08291229 successfully
I0829 04:36:14.835621 9 manager.go:389] backup cluster tidb-tianji-new/tianjing-db-backup-08291229 data to s3://xxx-tidb-backup-s3/TiDB-tianji-new=xxx_db/offline/202408291230 success
I0829 04:36:14.918097 9 manager.go:418] Get br metadata for backup files in s3://xxx-tidb-backup-s3/TiDB-tianji-new=xxx_db/offline/202408291230 of cluster tidb-tianji-new/tianjing-db-backup-08291229 success
I0829 04:36:14.918123 9 manager.go:422] Get size 376 for backup files in s3://xxx-tidb-backup-s3/TiDB-tianji-new=xxx_db/offline/202408291230 of cluster tidb-tianji-new/tianjing-db-backup-08291229 success
I0829 04:36:14.918134 9 manager.go:423] Get cluster tidb-tianji-new/tianjing-db-backup-08291229 commitTs 452173754081738758 success
I0829 04:36:14.927572 9 backup_status_updater.go:128] Backup: [tidb-tianji-new/tianjing-db-backup-08291229] updated successfully
云厂商的请求日志如此啊:
