Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: pd client 收不到 SplitAndScatterRegions 请求的响应
[TiDB Usage Environment] Testing
[TiDB Version] v6.5.0
[Reproduction Path] Calling golang pd client SplitAndScatterRegions API
[Encountered Problem: Phenomenon and Impact]
The request was sent, and the pd log shows that the request was received and the split was completed, but the client never receives a response.
- Client Code
- pd Log
An empty cluster wants to perform pre-splitting.
It would be better to insert some data to trigger the split. Without a proper scenario, the threshold conditions won’t be met, and it can’t be triggered.
Many parameters and conditions are interdependent and related, making it quite complex.
Trying to achieve this through debugging the code is a bit challenging… Good luck~~ (I can only support you in spirit
)
Haha, got it, thanks~
By the way, from what you said, it seems that adjusting configuration parameters like split size thresholds is meaningless, and we must try to modify the relevant code of PD+TiKV, right?
However, this design is not very good. Ideally, it should be able to pre-split directly; otherwise, it won’t be feasible to handle high traffic from the beginning.
There are two types: one is pre-split and the other is auto-split. These correspond to different models. Reading the documentation more should be helpful for you.
Yes, that’s right. Isn’t it about pre-splitting not working well? Without data, it doesn’t split. I didn’t use TiDB, just TiKV directly.