Help Center > > User Guide> FusionInsight Manager Operation Guide> Alarm Reference (Applicable to MRS 3.x)> ALM-12103 Executor Resource Exception

ALM-12103 Executor Resource Exception

Updated at: Mar 25, 2021 GMT+08:00


HA checks the Executor resources of Manager every 30 seconds. This alarm is generated when HA detects that the Executor resources are abnormal for two consecutive times.

This alarm is cleared when the Executor resources are normal.

Resource Type of Executor is Single-active. Active/standby will be triggered upon resource exceptions. When this alarm is generated, the active/standby switchover is complete and new Executor resources have been enabled on the new active Manager. In this case, this alarm is cleared. This alarm is used to notify users of the cause of the active/standby Manager switchover.


Alarm ID

Alarm Severity

Auto Clear








Specifies the cluster or system for which the alarm is generated.


Specifies the name of the service for which the alarm is generated.


Specifies the name of the role for which the alarm is generated.


Specifies the name of the host for which the alarm is generated.

Impact on the System

  • The active/standby Manager switchover occurs.
  • The Executor process keeps restarting. As a result, the cluster page may fail to be accessed.

Possible Causes

The Executor process is abnormal.


Check whether the Executor process is abnormal.

  1. In the alarm list on FusionInsight Manager, locate the row that contains the alarm, and click to view the name of the host for which the alarm is generated.
  2. Log in to the host for which the alarm is generated as user root.
  3. Run the su - omm command to switch to user omm.
  4. Run the sh ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/hacom/script/ command to check whether the status of the Executor resources managed by the HA is normal. In the single-node system, the Executor resource is in the normal state. In the dual-node system, the Executor resource is in the normal state on the active node and in the stopped state on the standby node.

    • If yes, go to 7.
    • If no, go to 5.

  5. Run the vi $BIGDATA_LOG_HOME/omm/oms/ha/scriptlog/executor.log command to check whether the Executor resource log of HA contains the keyword ERROR. If yes, analyze the log to locate the resource exception cause and fix the exception.
  6. After 5 minutes, check whether this alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 7.

Collect fault information.

  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
  2. In the Services area, select Controller and OmmServer, and click OK.
  3. 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.
  4. Contact O&M personnel and provide the collected logs.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?

Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel