TiDB 6.1.0 Version Restore Failure

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tidb6.1.0版本恢复失败

| username: TiDBer_BwNZ5U9X

br tool recovery, can anyone tell me why this error occurred again?

…> 41.67% Full Restore <--------------------------------.…> 41.67% Full Restore <--------------------------------|…> 41.67% Full Restore <-----------------------------------------------------------------------------> 100.00% [2023/08/31 08:43:22.824 +08:00] [INFO] [collector.go:69] [“Full Restore failed summary”] [total-ranges=1] [ranges-succeed=0] [ranges-failed=1] [split-region=1.178651ms] [restore-ranges=26] [unit-name=file] [error=“rpc error: code = Unavailable desc = keepalive watchdog timeout; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader; rpc error: code = Unavailable desc = not leader”] [errorVerbose="the following errors occurred:\n - rpc error: code = Unavailable desc = keepalive watchdog timeout\n github.com/pingcap/errors.AddStack\n \t/go/pkg/mod/github.com/pingcap/errors@v0.11.5-0.20211224045212-9687c2b0f87c/errors.go:174\n

| username: tidb菜鸟一只 | Original post link

Is the cluster status normal?

| username: TiDBer_BwNZ5U9X | Original post link

No problem

| username: 像风一样的男子 | Original post link

Is the restored database an empty database? During the restoration, it is also necessary to ensure that no other data is being written.

| username: redgame | Original post link

At first glance, it appears that the RPC communication between the BR tool and the node has timed out.