[dr-autosync] switch to backup dc during sync_recover mode, flashback panic due to no leader for one region #6715
Labels
type/feature-request
Categorizes issue or PR as related to a new feature.
Bug Report
What did you do?
Switch to backup dc during sync_recover mode, do online recovery, and flashback in the new backup cluster.
What did you expect to see?
What did you see instead?
[root@tiup-0 ~]# tiup ctl:v6.5.3 tikv --pd pd3-peer.e2e-dr-auto-sync-5r-func-tps-1744499-1-8:2379 flashback -v 442490139984003200
Starting component
ctl
: /root/.tiup/components/ctl/v6.5.3/ctl /root/.tiup/components/ctl/v6.5.3/ctl tikv --pd pd3-peer.e2e-dr-auto-sync-5r-func-tps-1744499-1-8:2379 flashback -v 442490139984003200thread 'flashback' panicked at 'called
Result::unwrap()
on anErr
value: Other("[components/pd_client/src/util.rs:878]: invalid store ID 0, not found")', cmd/tikv-ctl/src/main.rs:820:62note: run with
RUST_BACKTRACE=1
environment variable to display a backtracethread 'main' panicked at 'called
Result::unwrap()
on anErr
value: JoinError::Panic(Id(9), ...)', cmd/tikv-ctl/src/main.rs:945:6Error: exit status 101
Above error cause by following region.
What version of PD are you using (
pd-server -V
)?sh-4.2# ./pd-server -V
Release Version: v6.5.3-hotfix0627
Edition: Community
Git Commit Hash: 22e04ce
Git Branch: heads/refs/tags/v6.5.3-hotfix0627
UTC Build Time: 2023-06-27 03:13:08
Seems it caused by cluster change to async after pd allocate id for region split and before region split started in tikv.
The text was updated successfully, but these errors were encountered: