# [FAQ] 删除无效告警 TiKV_coprocessor_request_error 为 lock

## Key Words

TiKV_coprocessor_request_error, lock

## Description

### 告警信息

```yaml
Alert:
Reporter: name-alerts@{company-name}.com
Breach: Status="firing"
alertname="TiKV_coprocessor_request_error"
env="egv-transactions-ch"
expr="increase(tikv_coprocessor_request_error{reason!="lock"}[10m]) > 5000"
instance="cluster-name-tikv-id"
kubernetes_namespace="name-clusters-prod"
reason="meet_lock"
cluster="cluster-name"
component="tikv"
job="name-clusters-prod-cluster-name-tikv"
level="warning"
prometheus_replica="name-clusters-prod_cluster-name-monitor-0"
tidb_cluster="name-clusters-prod-cluster-name"
description="cluster: cluster-name, reason: meet_lock, instance: name-clusters-prod-cluster-name-tikv, values: 5632.820512820513"
summary="TiKV coprocessor request error"
value="5632.820512820513"
startsAt="2022-10-10T12:51:49.907Z", endsAt="0001-01-01T00:00:00Z", Fingerprint="a1413a260d86a604", GeneratorURL="http://egv-transactions-ch-monitor-1:9090/graph?g0.expr=increase%28tikv_coprocessor_request_error%7Breason%21%3D%22lock%22%7D%5B10m%5D%29+%3E+5000&g0.tab=1"
Breaching AppId: name
Zone: name
```

## Content

在新版本的 TiKV 默认告警告警模版中已经删除 coprocessor meet lock 的告警，原因是在 coprocessor 中遇到锁的情况在 Percolator 事务模式中是预期的，对实际的读写请求没有影响。

Github PR: <https://github.com/tikv/tikv/pull/11614>

## Affected Versions

< v4.0.16
< v5.0.6
< v5.1.5
< v5.2.4