Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: failed to handle split req v6.1.0
【TiDB Environment】Production
【TiDB Version】v6.1.0
【Encountered Issue】no valid key found for split
【Reproduction Path】Basically did nothing, just DM synchronized two projects
【Problem Phenomenon and Impact】
[2022/07/16 07:18:35.256 +08:00] [ERROR] [split_observer.rs:142] [“failed to handle split req”] [err=“"no valid key found for split."”] [region_id=137404]
[2022/07/16 07:18:35.256 +08:00] [WARN] [peer.rs:4205] [“skip proposal”] [error_code=KV:Raftstore:Coprocessor] [err=“Coprocessor(Other("[components/raftstore/src/coprocessor/split_observer.rs:147]: no valid key found for split."))”] [peer_id=137407] [region_id=137404]
I have seen a similar post before, you can refer to it failed to handle split req v6.1.0 - TiDB 的问答社区
There is a bit of an issue with the link; the link is the link to this post.
Sure, please provide the text you need translated from Chinese to English.
tiup ctl:v6.1.0 pd -u 120.12.10.19:2379 region 137404
The version is 6.1.0. The region in the screenshot above is normal, right?
It is fixed in several regions.
The prompt indicates a split key issue. The split process first checks whether to split, calculates the split key, then applies for a region ID from PD, and constructs new region information based on the relevant ID. You can check the detailed information in the logs of the relevant components.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.