ALM-24004 Exception Occurs When Flume Reads Data¶
Description¶
The alarm module monitors the status of Flume Source. This alarm is generated immediately when the duration in which Source fails to read the data exceeds the threshold.
The default threshold is 0, indicating that the threshold is disabled. You can change the threshold by modifying the properties.properties file in the conf directory. Specifically, modify the NoDatatime parameter of required the source.
The alarm is cleared when Source reads the data and the alarm handling is complete.
Attribute¶
Alarm ID | Alarm Severity | Auto Clear |
|---|---|---|
24004 | Major | Yes |
Parameters¶
Name | Meaning |
|---|---|
Source | Specifies the cluster for which the alarm is generated. |
ServiceName | Specifies the service for which the alarm is generated. |
HostName | Specifies the host for which the alarm is generated. |
AgentId | Specifies the ID of the agent for which the alarm is generated. |
ComponentType | Specifies the component type for which the alarm is generated. |
ComponentName | Specifies the component name for which the alarm is generated. |
Impact on the System¶
If data is found in the data source and Flume Source continuously fails to read data, the data collection is stopped.
Possible Causes¶
Flume Source is faulty, so data cannot be sent.
The network is faulty, so the data cannot be sent.
Procedure¶
Check whether Flume Source is faulty.
Open the properties.properties configuration file on the local PC, search for keyword type = spooldir in the file, and check whether the Flume source type is spoolDir.
View the spoolDir directory to check whether all files are already transferred.
If yes, no further action is required.
If no, go to 5.
Note
The monitoring directory of spooDir is specified by the .spoolDir parameter in the properties.properties configuration file. If all files in the monitoring directory have been transferred, the file name extension of all files in the monitoring directory is .COMPLETED.
Open the properties.properties configuration file on the local PC, search for org.apache.flume.source.kafka.KafkaSource in the file, and check whether the Flume source type is Kafka.
Check whether the topic data configured by Kafka Source has been used up.
If yes, no further action is required.
If no, go to 5.
On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > Flume > Instance.
Go to the Flume instance page of the faulty node to check whether the indicator Source Speed Metrics in the alarm is 0.
Check the network connection between the faulty node and the node that corresponds to the Flume Source IP address.
Open the properties.properties configuration file on the local PC, search for type = avro in the file, and check whether the Flume source type is Avro.
Log in to the faulty node as user root, and run the ping IP address of the Flume source command to check whether the peer host can be pinged successfully.
Contact the network administrator to restore the network.
In the alarm list, check whether the alarm is cleared after a period.
If yes, no further action is required.
If no, go to 11.
Collect the fault information.
On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
Expand the Service drop-down list, and select Flume for the target cluster.
Click
in the upper right corner, and set Start Date and End Date for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click Download.Contact O&M personnel and provide the collected logs.
Alarm Clearing¶
This alarm is automatically cleared after the fault is rectified.