DR-autosync: region cannot be SIMPLE_MAJORITY after recover to sync mode

[mayjiang0203]

Bug Report

What did you do?

#PD-DR-08-4#

What did you expect to see?

What did you see instead?

Some of region stay in SIMPLE_MAJORITY even pd work in sync mode.
[2021/08/19 14:04:51.975 +08:00] [INFO] [pdutil.go:254] ["No need to wait to recover to sync,cur stat:sync"]
[2021/08/19 14:04:52.154 +08:00] [WARN] [pdutil.go:364] ["There are 7 regions not in expected status."]
[2021/08/19 14:04:52.154 +08:00] [WARN] [pdutil.go:365] ["Regions stay not in expected status:NTEGRITY_OVER_LABEL|UNKOWN v%!(NOVERB)%!(EXTRA map[int]string=map[188:SIMPLE_MAJORITY 224:SIMPLE_MAJORITY 228:SIMPLE_MAJORITY 232:SIMPLE_MAJORITY 252:SIMPLE_MAJORITY 307:SIMPLE_MAJORITY 319:SIMPLE_MAJORITY])"]

What version of PD are you using (pd-server -V)?

/ # /pd-ctl -V
Release Version: v5.2.0-nightly
Edition: Community
Git Commit Hash: 0c56677
Git Branch: heads/refs/tags/v5.2.0-nightly
UTC Build Time: 2021-08-18 10:40:56

sh-4.2# ./tikv-server -V
TiKV
Release Version: 5.1.0-alpha
Edition: Community
Git Commit Hash: 941ce280fb869b542ea68a1176299074352ca8b6
Git Commit Branch: debug-dr
UTC Build Time: 2021-08-09 12:37:59
Rust Version: rustc 1.56.0-nightly (2faabf579 2021-07-27)
Enable Features: jemalloc mem-profiling portable sse protobuf-codec test-engines-rocksdb cloud-aws cloud-gcp
Profile: release

[mayjiang0203]

/severity major
/assign @nolouch

[nolouch]

ref tikv/tikv#10772