• MapReduce Service

mrs
  1. Help Center
  2. MapReduce Service
  3. User Guide
  4. MRS Manager Operation Guide
  5. Alarm Reference
  6. ALM-27004 Data Inconsistency Between Active and Standby DBServices

ALM-27004 Data Inconsistency Between Active and Standby DBServices

Description

The system checks the data synchronization status between the active and standby DBServices every 10 seconds. This alarm is generated when the synchronization status cannot be queried six times consecutively or when the synchronization status is abnormal. This alarm is cleared when data synchronization is normal.

Attribute

Alarm ID

Alarm Severity

Automatically Cleared

27004

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.

Local DBService HA Name

Specifies a local DBService HA.

Peer DBService HA Name

Specifies a peer DBService HA.

SYNC_PERSENT

Specifies the synchronization percentage.

Impact on the System

Data may be lost or abnormal if the active instance becomes abnormal.

Possible Causes

  • The network between the active and standby nodes is unstable.
  • The standby DBService is abnormal.
  • The disk space of the standby node is full.

Procedure

  1. Check whether the network between the active and standby nodes is in the normal state.

    1. Log in to MRS Manager, click Alarm, click the row where the alarm is located in the alarm list, and view the IP address of the standby DBService in the alarm details.
    2. Log in to the active DBService node.
    3. Run the ping heartbeat IP address of the standby DBService command to check whether the standby DBService node is reachable.
      • If yes, go to 2.a.
      • If no, go to 1.d.
    4. Contact the public cloud O&M personnel to check whether the network is faulty.
      • If yes, go to 1.e.
      • If no, go to 2.a.
    5. Rectify the network fault and check whether the alarm is cleared from the alarm list.
      • If yes, no further action is required.
      • If no, go to 2.a.

  2. Check whether the standby DBService is in the normal state.

    1. Log in to the standby DBService node.
    2. Run the following command to switch the user:

      sudo su - root

      su - omm

    3. Go to the ${DBSERVER_HOME}/sbin directory and run the ./status-dbserver.sh command to check whether the GaussDB resource status of the standby DBService is in the normal state. In the command output, check whether the following information is displayed in the row where ResName is gaussDB:

      For example:

      10_10_10_231 gaussDB Standby_normal Normal Active_standby

  3. Check whether the disk space of the standby node is insufficient.

    1. Use PuTTY to log in to the standby DBService node as user root.
    2. Run the su - omm command to switch to user omm.
    3. Go to the ${DBSERVER_HOME} directory, and run the following commands to obtain the DBService data directory:

      cd ${DBSERVER_HOME}

      source .dbservice_profile

      echo ${DBSERVICE_DATA_DIR}

    4. Run the df -h command to check the system disk partition usage.
    5. Check whether the DBService data directory space is full.
    6. Perform an upgrade and expand the capacity.
    7. After capacity expansion, wait 2 minutes and check whether the alarm is cleared.
      • 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