Help Center/ MapReduce Service/ User Guide/ MRS Cluster O&M/ MRS Cluster Alarm Handling Reference/ ALM-45294 RangerKMS Process Is Abnormal
Updated on 2024-11-13 GMT+08:00
View PDF
Share

ALM-45294 RangerKMS Process Is Abnormal

This section is available for MRS 3.3.1 or later version only.

Alarm Description

The RangerKMS process checks the process status every 20 seconds. This alarm is generated when the process status is abnormal and does not recover for a long time.

This alarm is cleared when the process status recovers.

Alarm Attributes

Alarm ID

Alarm Severity

Auto Cleared

45294

Major

Yes

Alarm Parameters

Type

Parameter

Description

Location Information

Source

Specifies the cluster for which the alarm was generated.

ServiceName

Specifies the service for which the alarm was generated.

RoleName

Specifies the role for which the alarm was generated.

HostName

Specifies the host for which the alarm was generated.

Additional Information

Trigger Condition

Specifies the alarm triggering condition.

Impact on the System

If the process status is abnormal, the process cannot provide services properly. As a result, the entire service may become abnormal.

Possible Causes

The host responds slowly to I/O (disk I/O and network I/O) requests and some processes are in the D state and Z state. The process may also be suspended and enter the T state.

Handling Procedure

Check whether the process is in the D, Z, or T state.

  1. Log in to FusionInsight Manager and choose O&M > Alarm > Alarms. Wait for about 10 minutes and check whether the alarm is automatically cleared.

    • If the alarm is not in the list, no further action is required.
    • If the alarm is in the list, view the alarm details and record the IP address of the host where the alarm is generated. Run the command in 2.

  2. Log in to the host where the alarm is generated as the root user and run the su - omm command to switch to the omm user.
  3. Run the following command to check the process state:

    ps ww -eo stat,cmd| grep -w Dproc_rangerkms | grep -v grep | awk '{print$1}'

  4. Check whether the command output contains any abnormal state (D, Z, or T).

    • If the output contains any abnormal state, go to 5.
    • If the output does not contain abnormal states, go to 7.

  5. Switch to user root and run the reboot command to restart the host for which the alarm is generated. (Restarting a host is risky. Ensure that the service process is normal after the restart.)
  6. Wait 5 minutes and check whether the alarm is cleared.

    • If the alarm is cleared, no further action is required.
    • If the alarm fails to be cleared, go to 7.

Collect fault information.

  1. On FusionInsight Manager, choose O&M. In the navigation pane on the left, choose Log > Download.
  2. Expand the drop-down list next to the Service field. In the Services dialog box that is displayed, select Ranger for the target cluster.
  3. 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.
  4. Contact O&M engineers and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None.