Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: pd参数配置问题
[TiDB Usage Environment] Production Environment
[TiDB Version] 6.5.7
Using the show config
command to check the PD configuration, you can see the max-request-bytes
configuration item. However, there is no information about this parameter in the official documentation.
Used to control the maximum number of bytes for a single SQL request.
Is it similar to max_allowed_packet?
You can view the source code of TiDB.
I encountered this issue before as well, but I didn’t address it. The cluster is functioning quite normally now.
It should be a parameter that does not support modification, so there is no documentation.
bad request to http://10.0.0.13:2379/pd/api/v1/config: “config prefix max-request-bytes not found”
default max bytes for grpc message, but it looks like using unsafe recovery in a large cluster will be limited by this
The link you provided points to the configuration file in the TiKV PD repository on GitHub. Specifically, it refers to line 144 in the config.go
file.
It is probably a hidden parameter configuration, which should not be modified, only viewed.
The maximum number of bytes. Haven’t used it before…
Have you studied this deeply? I’m just getting started.
It’s better not to change the parameters that are not officially recommended.
The official documentation does not recommend modifying this parameter.
Be careful to verify in the test environment.
Can pdctl be successfully modified?