Description
When you upgrade OceanBase Cloud Platform (OCP), you must also upgrade OCP-Agent. If OCP-Agent fails to be upgraded, this alert is generated.
Alert parameters
| Parameter | Value |
|---|---|
| Metric | None |
| Source | None |
| Collected metric | None |
| Metric expression | None |
| Collection cycle | None |
Alert rule
| Metric expression | Metric description | Default threshold | Detection cycle | Time before clearance |
|---|---|---|---|---|
| None | None | None | None | 5 minutes |
Alert information
| Trigger method | Alert level | Scope |
|---|---|---|
| Based on the expression of the metric | Critical | Service |
Alert templates
Overview
- Template: ${alarm_target} ${alarm_name}
- Sample: alarm_template_id=0:host_count=2 upgrade_ocp_agent_failed
Details
- Template: Alert: ${alarm_name}. Host list: ${hosts}.
- Sample: Alert: upgrade_ocp_agent_failed. Host list: xxx.xxx.xxx.xxx,xxx.xxx.xxx.xxx
Impact on the system
OCP-Agent is a process deployed on a host that is taken over by OCP. It comprises a management (O&M) process and a monitoring process. If OCP-Agent fails to be upgraded, the version of OCP-Agent will be inconsistent with that of OCP-Server and the following issues will be caused:
- O&M operations, such as routine O&M operations on OceanBase Database, OceanBase Proxy (OBProxy), and hosts, cannot be performed.
- Monitoring data of the later version cannot be collected.
Possible causes
An upgrade may fail due to different causes. You must perform analysis based on the actual situation.
Solutions
Contact engineers on duty for help.
