Contents1 Introduction
This instruction concerns alarm handling for the Storage Engine, Execution of Selective Replica Check Failed, PLDB, Major alarm.
1.1 Alarm Description
The alarm is raised when Selective Replica Check was not able to retrieve all applicable entries when analyzing the operational logs for the database cluster .
For further information about Selective Replica Check, refer to CUDB Data Storage Handling.
The alarm is issued in the following situations:
The possible alarm causes and the corresponding fault reasons, fault locations and impacts are described in Table 1 .
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
|---|---|---|---|---|
|
Time gaps in the operational logs. |
Certain events in the CUDB can cause failures when writing in the operational logs. |
If a process that is responsible for writing in an operational log, crashes or is in any way prevented from writing, not all relevant information is provided in the operational logs. |
Operational logs on the former master replica. |
There is a possibility that all the changes to the data in the database cluster were not detected by Selective Replica Check. |
The following are the consequences for the node if the alarm is raised:
The alarm attributes are listed and explained in Table 2:
|
Attribute Name |
Attribute Value |
|---|---|
|
Auto Cease |
No |
|
Module |
STORAGE-ENGINE |
|
Error Code |
27 |
|
Timestamp First |
Date and time when the alarm was raised for the first time. |
|
Repeated Counter |
Number which indicates how many times the alarm was raised. |
|
Timestamp Last |
Date and time of the most recent alarm raised. |
|
Resource ID |
.1.3.6.1.4.1.193.169.1.1.27.<Timestamp> |
|
Alarm Model Description |
Execution of Selective Replica Check Failed, Storage Engine. |
|
Alarm Active Description |
Storage Engine (PLDB): Selective Replica Check failed, task <Task ID>. It was not possible to retrieve all applicable entries. |
|
ITU Alarm Event Type |
processingErrorAlarm (4) |
|
ITU Alarm Probable Cause |
databaseInconsistency (160) |
|
ITU Alarm Perceived Severity |
(4) – Major |
|
Originating Source IP |
Node ID where the alarm was raised. |
|
Sequence Number |
Number which indicates the order in which alarms were raised. |
In Table 2, the indicated variables are as follows:
For more information about attributes description, refer to CUDB Node Fault Management Configuration Guide.
1.2 Prerequisites
This section provides information on the documents, tools, and conditions that apply to the procedure.
1.2.1 Documents
Before starting this procedure, ensure that you have read the following documents:
1.2.2 Tools
Not applicable.
1.2.3 Conditions
Not applicable.
2 Procedure
Steps
Do the following:
- If the Storage Engine, Unable to Synchronize Cluster in PLDB, Major alarm is raised when the Self-Ordered Backup and Restore function is not enabled or fails to restore the replication automatically, follow the procedure described in Storage Engine, Unable To Synchronize Cluster In PLDB, Major.
- Cease the alarm manually.
Results
| Note: |
The procedure is to fix data inconsistency among master and slave replicas, but it cannot
guarantee the full repair of system data. |