Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: TIDB DASHBOARD显示报警，请问怎么解决
|
username: TiDBer_8xw9Q7ml
Sorry, I cannot translate images. Please provide the text content you need translated.
You have a lot of issues here. Generally, you don’t need to worry about those on the dashboard. Is this environment a test environment? Are the configurations set according to the official recommendations? Did you follow the official installation steps?
How exactly can this be resolved? There are only alerts at the moment, no other error issues yet.
Check the configuration for that config, don’t worry about the rest.
Transparent HugePages can cause memory allocation delays at runtime, so it is recommended to disable Transparent HugePages on all TiDB servers. Should this be disabled?
There won’t be any issues if there are too many alerts, right?
The official recommendation is to turn it off TiDB 环境与系统配置检查 | PingCAP 文档中心
It is recommended to disable it, you can refer to the following methods:
THP is enabled, please disable it for best performance Transparent Hugepages (THP) is a Linux memory management system that reduces the overhead of Translation Lookaside Buffer (TLB) lookups on computers with large amounts of memory by using larger memory pages. However, database workloads typically perform poorly on THP because they tend to have sparse rather than contiguous memory access patterns. You should disable THP on Linux machines to ensure optimal performance. It is recommended to disable this feature.
FIX:
|
username: 
|
username: 
|
username: echo never > /sys/kernel/mm/transparent_hugepage/enabled
echo never > /sys/kernel/mm/transparent_hugepage/defrag
cat /sys/kernel/mm/transparent_hugepage/enabled
always madvise [never]
What are the other alerts, and why are they triggered?
You can use this command to check the operating system configuration (note to replace mytidb with your cluster name)
tiup cluster check mytidb --cluster
Do I need to address all the warnings and failures?
Compare the rules and see, generally those with little impact on the application can be ignored… INSPECTION_RESULT | PingCAP 文档中心
Since we have 4 nodes, will restarting one PD affect the others?
You can try automatic repair first using --apply (note to replace mytidb with your cluster name).
For example: tiup cluster check mytidb --cluster --apply
Restarting only the leader node of PD may have a slight impact on the business because a leader switch is required, but restarting other nodes does not affect the business.
|
username: 
|
username: