Alert description
This alert is triggered when the actual name of an OceanBase tenant in the cluster does not match the tenant name recorded in the OCP MetaDB. It is triggered when OCP synchronizes tenant information and discovers that a tenant has been renamed on the OceanBase side, but the old name is still displayed in OCP, prompting administrators to pay attention and synchronize the tenant names.
Alert principle
Parameter |
Value |
|---|---|
| Monitoring Metrics | N/A |
| Monitoring Expression | N/A |
| Metric Collection | N/A |
| Metric Source | OCP Scheduled Tenant Synchronization Task Trigger (runs again after a 60-second delay after each completion) |
| Collection Cycle | N/A |
Rule information
Monitoring Metrics |
Default Threshold |
Duration |
Detection Cycle |
Elimination Cycle |
|---|---|---|---|---|
| N/A | N/A | N/A | N/A | 5 Minutes |
Alert information
Alert Trigger Method |
Alert Level |
Scope |
|---|---|---|
| Maintenance Event Trigger | Critical | Tenant |
Alert template
Alert overview
- Template: ${alarm_target} ${alarm_name}
- Example: ob_cluster=obcluster1:tenant_name=old_tenant:ob_tenant_id=1001 The tenant name of the OceanBase tenant has changed.
Alert details
- Template: Cluster: ${ob_cluster_name}, Tenant: ${tenant_name}:${ob_tenant_id}, Alert: ${alarm_name}. The tenant name of tenant ${tenant_name}:${ob_tenant_id} has changed to ${actual_tenant_name}.
- Example: Cluster: obcluster1, Tenant: old_tenant:1001, Alert: The tenant name of the OceanBase tenant has changed. The tenant name of tenant old_tenant:1001 has changed to new_tenant.
Impact on the system
Tenant name inconsistency may cause:
Incorrect tenant name displayed in OCP: The console, monitoring, and other interfaces still show the old tenant name, which does not match the actual OceanBase tenant name. This can lead to misoperations or misjudgments.
Synchronization and O&M limitations: If the tenant name does not match, OCP skips the synchronization of tenant information, which may cause metadata to become outdated. As a result, some O&M or update operations that depend on the tenant name may fail.
Possible causes
Renaming operations such as
ALTER TENANT ... RENAME GLOBAL_NAME TO ...were performed on the OceanBase side, but OCP was not updated accordingly.When managing the same cluster across multiple environments or OCP instances, modifying the tenant name separately on one side causes inconsistency between OCP metadata and the actual cluster state.
Solution
Confirm the alert information: Verify which tenant has undergone a rename based on the cluster name (ob_cluster_name), OCP-side tenant name (tenant_name), tenant ID (ob_tenant_id), and actual name (actual_tenant_name) provided in the alert.
Confirm whether the change is as expected: In OceanBase Database, confirm the current name of the tenant:
SELECT tenant_id, tenant_name FROM oceanbase.DBA_OB_TENANTS WHERE tenant_id = <ob_tenant_id>;If tenant_name is already actual_tenant_name, it means the name has been changed on the OceanBase side but has not yet been synchronized to OCP.
On the details or edit page of the tenant in the OCP console, change the tenant name to actual_tenant_name (the same as the one in OceanBase Database). Save the changes and wait for the next synchronization; the alert should be resolved.
If you want to retain the name on the OCP side: You need to change the tenant name back to the one recorded in OCP on the OceanBase side (you must assess the impact on business connection strings and application configurations). After changing it back, synchronize again and the alert will disappear.
Verification: After confirming that the tenant name on OCP matches the one in OceanBase, the alert will automatically clear within its clearance period (300 seconds). If it persists, check whether there are multiple historical alerts or if other tenants also have inconsistent names.