Interstage Big DataParallel Processing ServerV1.0.1 User's Guide

Chapter 15 Operations when There are Errors

This chapter describes the corrective action to take when an error occurs on a system that uses this product.

Possible errors that may occur with this product are shown below.

Error details	Possible issue
System error (physical machine) (*1)	System panic occurred System has stopped due to forced power off or other cause System has stopped responding
System error (virtual machine)	Virtual machine panic occurred Virtual machine has stopped responding
Public LAN network error (*2)	Hardware error such as a faulty NIC or cable An error has occurred in the public LAN transmission route (*3)
Cluster interconnect (CIP) error (*2)	Hardware error such as a faulty NIC or cable Heartbeat monitoring detected an error between the primary master server and the secondary master server
iSCSI network error (*2)	Hardware error such as a faulty NIC or cable Error has occurred in the iSCSI-LAN transmission route
JobTracker error	JobTracker process has ended in an error JobTracker process was stopped by a means other than the bdpp_stop command (*4)

*1: Indicates an error on the physical environment server or on the virtual environment host machine.

*2: If a LAN uses redundancy, indicates that an error has occurred on both LANs.

*3: Errors are detected differently depending on the feature used for redundancy.

*4: Indicates the direct use of the Apache Hadoop feature to stop the JobTracker.

The following sections explain how these errors affect each server, and the corresponding action that should be taken.

• Operations when Errors Occur on a Master Server

• Operations when Errors Occur on a Slave Server

• Operations when Errors Occur on a Development Server

• Operations when Errors Occur on a Collaboration Server

  
  

This chapter also contains a section that describes how to perform operations when errors occur on a file system.

Additionally, reference information on checking error occurrences is provided.

• Operations when Errors Occur on the File System

• How to Check Errors

See

• Refer to "2.4 Monitoring function of NIC switching mode" in the "PRIMECLUSTER Global Link Services Configuration and Administration Guide 4.3 Redundant Line Control Function" for information on detecting public LAN errors in network redundancy software (redundancy in a physical environment).
  If required, also refer to "Checking network replication status".

• Refer to the manual for the virtualization software product you are using for information on the NIC teaming feature (redundancy in a virtual environment).