Description
When tenant compaction is enabled in OceanBase Database V4.0 and later, this alert is triggered when an error occurs during tenant compaction.
Principle
Parameter |
Value |
|---|---|
| Monitoring metric | compaction_is_error |
| Metric source | Collected from internal views. SQL statement: select tenant_id, case is_error when 'YES' then 1 else 0 end as is_error from CDB_OB_MAJOR_COMPACTION |
| Collected metric | ob_compaction_is_error |
| Monitoring expression | max(ob_compaction_is_error{@LABELS}) by (@GBLABELS) |
| Collection interval | 1 minute |
Rule information
Monitoring expression |
Description of the monitoring metric |
Default threshold |
Detection period |
Elimination period |
|---|---|---|---|---|
| compaction_is_error == 1 | 1 | 60 seconds | 5 minutes |
Alert information
Alert triggering method |
Alert level |
Scope |
|---|---|---|
| Based on the expression of the monitoring metric | Severe | Tenant |
Alert template
Alert summary
- Template: ${alarm_target} ${alarm_name}
- Example: ob_cluster=C1-1000:tenant_name=T1 OceanBase tenant compaction error
Alert details
- Template: Cluster: ${ob_cluster_name}, Tenant: ${tenant_name}, Alert: ${alarm_name}.
- Example: Cluster: obcluster, Tenant: T1, Alert: OceanBase tenant compaction error.
Alert recovery
- Template: Alert: ${alarm_name}, OceanBase tenant compaction error flag: ${recover_value}
- Example: Alert: OceanBase tenant compaction error, OceanBase tenant compaction error flag: 0
Impact on the system
This can cause data inconsistencies in some replicas of the OceanBase cluster, such as inconsistencies between replicas or between the main table and the index table.
Possible causes
This is an extreme scenario that theoretically exists and has no common causes.
Solution
For more information, see Handle tenant compaction errors in an OceanBase cluster.
Notice
Improper handling may result in data inconsistencies. If you are not a professional, contact technical support for assistance.