• MapReduce Service

mrs
  1. Help Center
  2. MapReduce Service
  3. User Guide
  4. MRS Manager Operation Guide
  5. Alarm Reference
  6. ALM-27001 DBService Unavailable

ALM-27001 DBService Unavailable

Description

The alarm module checks the DBService status every 30 seconds. This alarm is generated when the system detects that DBService is unavailable and is cleared when DBService recovers.

Attribute

Alarm ID

Alarm Severity

Automatically Cleared

27001

Critical

Yes

Parameters

Parameter

Description

ServiceName

Specifies the service for which the alarm is generated.

RoleName

Specifies the role for which the alarm is generated.

HostName

Specifies the host for which the alarm is generated.

Impact on the System

The database service is unavailable and cannot provide data import or query functions for upper-layer services, which results in service exceptions.

Possible Causes

  • The floating IP address does not exist.
  • There is no active DBServer instance.
  • The active and standby DBServer processes are abnormal.

Procedure

  1. Check whether the floating IP address exists in the cluster environment.

    1. On MRS Manager, choose Service > DBService > Instance.
    2. Check whether the active instance exists.
      • If yes, go to 1.c.
      • If no, go to 2.a.
    3. Select the active DBServer instance and record the IP address.
    4. Log in to the host that corresponds to the preceding IP address, and run the ifconfig command to check whether the DBService floating IP address exists on the node.
      • If yes, go to 1.e.
      • If no, go to 2.a.
    5. Run the ping floating IPaddress command to check whether the DBService floating IP address can be pinged.
      • If yes, go to 1.f.
      • If no, go to 2.a.
    6. Log in to the host that corresponds to the DBService floating IP address, and run the ifconfig interface down command to delete the floating IP address.
    7. On MRS Manager, choose Service > DBService > More > Restart Service to restart DBService. Check whether DBService is restarted successfully.
      • If yes, go to 1.h.
      • If no, go to 2.a.
    8. Wait about 2 minutes and check whether the alarm is cleared from the alarm list.
      • If yes, no further action is required.
      • If no, go to 3.a.

  2. Check the status of the active DBServer instance.

    1. Select the DBServer instance whose role status is abnormal and record the IP address.
    2. On the Alarm page, check whether alarm ALM-12007 Process Fault occurs in the DBServer instance on the host that corresponds to the IP address.
    3. Follow procedures in ALM-12007 Process Fault to handle the alarm.
    4. Wait about 5 minutes and check whether the alarm is cleared from the alarm list.
      • If yes, no further action is required.
      • If no, go to Step 4.

  3. Check the status of the active and standby DBServers.

    1. Log in to the host that corresponds to the DBService floating IP address, and run the sudo su - root and su - omm commands to switch to user omm. Run the cd ${BIGDATA_HOME}/FusionInsight/dbservice/ command to go to the installation directory of DBService.
    2. Run the sh sbin/status-dbserver.sh command to view the status of DBService's active and standby HA processes. Check whether the status can be viewed successfully.
    3. Check whether the active and standby HA processes are normal.
    4. On MRS Manager, choose Service > DBService > More > Restart Service to restart DBService, and check whether DBService is restarted successfully.
    5. Wait about 2 minutes and check whether the alarm is cleared from the alarm list.
      • If yes, no further action is required.
      • If no, go to Step 4.

  4. Collect fault information.

    1. On MRS Manager, choose System > Export Log.
    2. Contact technical support engineers for help, detail see technical support.

Related Information

N/A