TiKV Log Contains Numerous WARN Entries "trying to deregister region not registered"

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

Original topic: tikv log 大量 warn 条目 “trying to deregister region not registered”

| username: Qiuchi

[TiDB Usage Environment] Production Environment
[TiDB Version] 6.5.0
[Reproduction Path] Regular Use
[Encountered Problem: Problem Phenomenon and Impact]
A large number of logs appear in tikv as shown in the picture

There are always region backoff (regionMiss) alerts in alertmanager

[Resource Configuration] 3db, 3pd, 6kv

| username: tidb狂热爱好者 | Original post link

Is there an error code for the service? Generally speaking, if you check often, the traffic graph is yellow.

| username: Qiuchi | Original post link

There is no malfunction, I just want to know what this entry means.

| username: Jiawei | Original post link

You can refer to the parameters at TiDB 集群报警规则 | PingCAP 文档中心. From your logs, it seems that the backoff is caused by a lock, which triggered the corresponding alert. You can check the TiKV logs to see if there is any lock waiting.

| username: Qiuchi | Original post link

The backoff is not a big deal; it should be caused by frequent truncation and reinsertion of many tables, resulting in a “region not found” message. I mainly want to know what “not registered” means and whether it is related to this.

| username: tidb狂热爱好者 | Original post link

Region did not find a leader.