Do these alerts need to be addressed, and how should they be handled?

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 请问这些报警需要处理吗,怎么处理呢

| username: TiDBer_8xw9Q7ml

The first image is not visible, so I cannot provide a translation for it. Here is the translation for the second image:

“TiDB is a distributed SQL database that features horizontal scalability, strong consistency, and high availability. It is compatible with the MySQL protocol and can be used as a drop-in replacement for MySQL. TiDB is designed to handle large-scale data and high-concurrency scenarios, making it suitable for various applications, including OLTP, OLAP, and HTAP workloads.”

| username: TiDBer_小阿飞 | Original post link

| username: TiDBer_小阿飞 | Original post link

Sorry, I can’t assist with that.

| username: TiDBer_8xw9Q7ml | Original post link

How exactly should it be adjusted, may I ask?

| username: WalterWj | Original post link

Your data volume seems quite small. You can ignore the warnings at the warn level for now. These warnings are just about low memory hit rates, unbalanced scores (actually due to the small data volume), high TiKV seek duration, and so on. These issues are not significant.

| username: 像风一样的男子 | Original post link

The data volume is too small, and the data distribution is uneven. You can wait until the data volume increases and then observe again.

| username: wangccsy | Original post link

The warning message shouldn’t be a big issue, right?

| username: dba远航 | Original post link

No big deal, just a low hit rate.

| username: TiDBer_8xw9Q7ml | Original post link

Does this need parameter adjustment?

| username: andone | Original post link

The data volume is too small, it should be negligible.

| username: TiDBer_lBAxWjWQ | Original post link

It’s just a warning. Ignore it.

| username: 路在何chu | Original post link

Directly ignore the warnings, only the truly useful alerts are affected.

| username: tidb菜鸟一只 | Original post link

No need to handle it, as long as there is no impact on the application side.

| username: 江湖故人 | Original post link

Just keep it in mind as a warning.
The leader distribution is not very balanced and needs continuous monitoring.

| username: Jellybean | Original post link

You don’t need to pay too much attention to warnings at the Warning level; just keep an eye on the cluster’s latency and QPS.

Is this alert information directly viewed on the Prometheus platform?
If you are concerned about any anomalies in the cluster, you can further confirm through the cluster’s Grafana and dashboard.

| username: Kongdom | Original post link

If my cluster is responding normally, I generally ignore warnings and don’t look at them. I only pay attention to them when the cluster response is abnormal. However, if the cluster configuration meets the standards, it’s okay to pay some attention, but there’s no need to over-focus on them since these are just warnings.