What is the cause of this error?

Translated
1

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

Original topic: 这个报错是怎么回事

| username: tidb狂热爱好者

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachments: Screenshots / Logs / Monitoring]
[FIRING:1] TiDB_schema_error
Labels
• alertname: TiDB_schema_error
• cluster: tidb-test
• env: tidb-test
• expr: increase(tidb_session_schema_lease_error_total{type=“outdated”}[15m]) > 0
• instance: 10.8.35.56:10080
• job: tidb
• level: emergency
• monitor: prometheus
• type: outdated
Annotations
• description: cluster: tidb-test, instance: 10.8.35.56:10080, values: 234.8654060606061
• summary: TiDB schema error
• value: 234.8654060606061
Source: http://10.8.35.62:9090/graph?g0.expr=increase(tidb_session_schema_lease_error_total{type%3D"outdated"}[15m])+>+0&g0.tab=1

2
| username: Jellybean | Original post link

TiDB_schema_error

  • Alert Rule: increase(tidb_session_schema_lease_error_total{type="outdated"}[15m]) > 0
  • Rule Description: TiDB did not reload the latest Schema information within a Lease period. If TiDB cannot continue to provide services, an alert is triggered.
  • Handling Method: This issue is usually caused by TiKV Region being unavailable or timing out. You need to check TiKV’s monitoring metrics to locate the problem.

Official Documentation: TiDB 集群报警规则 | PingCAP 文档中心

PS: If you encounter any problems, you can first search in the community search box. Usually, you will find answers that can solve the issue.