ALM-50809 Latency for StoreMaster to Notify StoreWorker of Data Deletion Exceeds the Threshold

Alarm Description

The system checks the latency for StoreMaster to notify the StoreWorker instances of deleting data every 30 seconds. This alarm is generated when the latency exceeds the threshold.

This alarm is cleared when the latency for StoreMaster to notify StoreWorker instances of deleting data is less than the threshold.

Alarm Attributes

Alarm Parameters

Impact on the System

If the latency exceeds the threshold, retry is triggered, which increases the load on the server.

Possible Causes

• The alarm threshold or alarm trigger count is improperly configured.
• The storage function of StoreWorker is abnormal.

Handling Procedure

Check whether the alarm threshold or alarm trigger count is properly configured.

1. Log in to FusionInsight Manager and choose O&M > Alarm > Thresholds > MemArtsStore > Latency > Latency of StoreMaster Deletion Notification to Workers.
2. Click the edit button next to Trigger Count, change the number based on site requirements, and click OK.
   

   Trigger Count specifies how many times the threshold can be hit before an alarm is generated.

3. Click Modify in the Operation column, change the alarm threshold based on site requirements, and click OK.
4. Wait 2 minutes and check whether the alarm is automatically cleared.
   • If yes, no further action is required.
   • If no, go to Step 5.

Collect fault information.

5. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
6. Expand the Service drop-down list, and select MemArtsStore for the target cluster.
7. Click the edit icon in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
8. Contact O&M engineers and send the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None