• MapReduce Service

mrs
  1. Help Center
  2. MapReduce Service
  3. User Guide
  4. MRS Manager Operation Guide
  5. Alarm Reference
  6. ALM-12039 GaussDB Data Is Not Synchronized

ALM-12039 GaussDB Data Is Not Synchronized

Description

The system checks the data synchronization status between the active and standby GaussDBs 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

12039

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 GaussDB HA IP

Specifies the HA IP address of the local GaussDB.

Peer GaussDB HA IP

Specifies the HA IP address of the peer GaussDB.

SYNC_PERSENT

Specifies the synchronization percentage.

Impact on the System

If the active instance becomes abnormal while data is not synchronized between the active and standby GaussDBs, data may be lost or abnormal.

Possible Causes

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

Procedure

  1. Log in to MRS Manager, click Alarm, locate the row that contains the alarm, and view the IP address of the standby GaussDB in the alarm details.
  2. Log in to the active management node.
  3. Run the following command to check whether the standby GaussDB is reachable:

    ping heartbeat IP address of the standby GaussDB

    If yes, go to Step 6.

    If no, go to Step 4.

  4. Contact the public cloud O&M personnel to check whether the network is faulty.

  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 Step 6.

  6. Log in to the standby GaussDB node.
  7. Run the following command to switch the user:

    sudo su - root

    su - omm

  8. Go to the ${BIGDATA_HOME}/om-0.0.1/sbin/ directory.

    Run the following command to check whether the resource status of the standby GaussDB is normal:

    sh status-oms.sh

    In the command output, check whether the following information is displayed in the row where ResName is  gaussDB:
    10_10_10_231 gaussDB Standby_normal Normal Active_standby

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

    sudo su - root

    su - omm

  3. Run the echo ${BIGDATA_DATA_HOME}/dbdata_om command to obtain the GaussDB data directory.
  4. Run the df -h command to check the system disk partition usage.
  5. Check whether the disk on which the GaussDB data directory is mounted is full.

  6. Contact the public cloud O&M personnel to expand the disk capacity. 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 15.

  7. 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