No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-37000 MPPDBServer Data Directory or Redo Directory Is Missing

ALM-37000 MPPDBServer Data Directory or Redo Directory Is Missing

Description

This alarm is generated if:

  • The data directory of a data instance is deleted.
  • The Redo directory (pg_xlog) of a data instance is deleted.

Attribute

Alarm ID

Alarm Severity

Auto Clear

37000

Major

Yes

Parameters

Name

Meaning

ServiceName

Identifies the service for which the alarm is generated.

RoleName

Identifies the role for which the alarm is generated.

HostName

Identifies the host for which the alarm is generated.

Instance

Identifies the instance for which the alarm is generated.

Impact on the System

The data instance cannot be started and the instance status is abnormal.

Possible Causes

The data directory or Redo log directory of the Coordinator or DataNode node is deleted.

Procedure

  1. Log in to the FusionInsight Manager.

    1. Log in to the ManageOne OM plane using a browser, then choose Alarms.
      • Login address: https://URL for the homepage of the ManageOne OM plane:31943. Example: https://oc.type.com:31943.
      • Default username: admin, default password: Huawei12#$.
    2. In the alarm list, locate and click the target alarm name in the Name column. The Alarm Details and Handling Recommendations dialog box is displayed.
    3. Locate the value in the IP Address/URL/Domain Name column, which is the float IP address of the FusionInsight Manager.
    4. Log in to the FusionInsight Manager using a browser.
      • Login address: https://float IP address of the FusionInsight Manager:28443/web. Example: https://10.10.192.100:28443/web.
      • Default username: admin, default password: obtain it from the system administrator.

  2. Check whether the data directory or Redo directory (pg_xlog) of the instance involved in this alarm is deleted.

    Run gs_om -t status --detail to obtain the data directory of each Coordinator or DataNode node in the cluster and the Redo directory under the data directory.

    1. On FusionInsight Manager, click Alarms. On the alarm list, locate the alarm and obtain the information about the node and instance for which the alarm is generated from Location in the Alarm Details area.
    2. Log in to the node where the alarm is generated as the omm user.

      Default user: omm, default password: Bigdata123@.

    3. Initialize the environment variables.

      source ${BIGDATA_HOME}/mppdb/.mppdbgs_profile

    4. Run the gs_om -t status --detail command.
      Information similar to the following is displayed:
      [  CMServer State   ]
      
      node     node_ip         instance                                    state
      ----------------------------------------------------------------------------
      1  host0 10.0.0.1    1    /opt/huawei/Bigdata/mppdb/cm/cm_server Primary
      
      [   Cluster State   ]
      
      cluster_state   : Normal
      redistributing  : No
      balanced        : Yes
      
      [ Coordinator State ]
      
      node     node_ip         instance                                  state
      --------------------------------------------------------------------------
      1  host0 10.0.0.1    5001 /srv/BigData/mppdb/data1/coordinator Normal
      
      [ Central Coordinator State ]
      
      node     node_ip         instance                                    state
      ----------------------------------------------------------------------------
      1  host0 10.0.0.1    5001 /srv/BigData/mppdb/data1/coordinator Normal
      
      [     GTM State     ]
      
      node     node_ip         instance                           state     
      ----------------------------------------------------------------------
      1  host0 10.0.0.1    1001 /opt/huawei/Bigdata/mppdb/gtm P Primary 
      [  Datanode State   ]
      
      node     node_ip         instance                                     state
      -----------------------------------------------------------------------------------------
      1  host0 10.0.0.1    6001 /srv/BigData/mppdb/data1/master1 P Primary Normal
      1  host0 10.0.0.1    6002 /srv/BigData/mppdb/data2/master2 P Primary Normal
      1  host0 10.0.0.1    6003 /srv/BigData/mppdb/data3/master3 P Primary Normal

  3. Recover the damaged data instance (Coordinator or DataNode). For details, see section "Rectifying an MPPDBServer Instance" in the Product Documentation.
  4. On FusionInsight Manager, choose Services > MPPDB > Instances.
  5. Select the faulty node and choose More Actions > Restart Instance. Wait for 5 minutes and check whether the alarm persists.

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

Collect fault information.

  1. On FusionInsight Manager, choose System > Log Download.
  2. Select MPPDB from the Services drop-down list box and click OK.
  3. Set Start Time for log collection to 1 hour ahead of the alarm generation time and End Time to 1 hour after the alarm generation time, and click Download.
  4. Contact Technical Support and send the collected logs.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 34575

Downloads: 31

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next