Hadoop monitoring is a Gateway configuration file that enables monitoring of the Hadoopcluster, nodes, and daemons through the JMX and Toolkit plug-ins.
This Hadoop integration template consists of the following components:
- Hadoop Distributed File System (HDFS)
- Yet Another Resource Negotiator (YARN)
The Hadoop Distributed File System or HDFS provides scalable data storage that can be deployed on hardware and optimised operations for large datasets.
The other component Yet Another Resource Negotiator or YARN assigns the computation resources for executing the application:
- YARN ResourceManager - takes inventory of available and allocate resources to running applications.
- YARN NodeManagers - monitors resource usage and communicates with the ResourceManager.
This guide discusses the steps to set up the Hadoop integration on a Gateway. Once the integration is set up, the samplers providing the dataviews become available to that Gateway.
To view the sample metrics and dataviews, see Hadoop Monitoring Technical Reference.
This monitoring template is a Gateway configuration setup that can be included in the Gateway Setup Editor.
To use this template, your configuration must meet the following requirements:
- Set up the HDFS with at least one DataNode.
- A machine running the Netprobe must have access to the Hadoop published HTTP address and port.
- An Active Console that is connected to the Gateway.
- Basic connectivity setup for JMX or Toolkit plug-in.
- Hadoop configuration files extracted to their Gateway set-up.
The following requirements must be met prior to the installation and setup of the template:
- Template package: geneos-integration-hadoop-<version>.zip.
- Managed entities utilising the samplers defined in the
- Apache Hadoop 3.0.0 or higher.
- Python 2.7 or higher.
For more information on supported versions, see Application and plug-in specific information in Geneos 5.x Compatibility Matrix.
This document is a reference guide to introduce templates and scripts built using the Geneos development toolkit plug-ins.
The template allows you to integrate specific applications and services to collect metrics without having to create a new plug-in.
- Administrator - oversees the administration and installation of the server.
- User - uses the Hadoop metrics via JMX plug-in to monitor the data and reports.
- Application Team - provides the connection settings for the JMX plug-in and queries for the Toolkit plug-in.
Ensure that you have read and can follow the system requirements prior to installation and setup of this integration template.
- Download the config file (geneos-integration-hadoop-<version>.zip) from the ITRS Downloads site.
- Open Gateway Setup Editor.
- In the Navigation panel, click Includes to create a new file.
- Enter the location of the file to include in the Location field. In this example, it is the
- Update the Priority field. This can be any value except
1. If you input a priority of
1, the Gateway Setup Editor returns an error.
- Expand the file location in the Includes section.
- Select Click to load.
- Click Yes to load the new Hadoop include file.
- Click Managed entities in the Navigation panel.
- Add the Hadoop-Cluster and Hadoop-Node types to the Managed Entity section that you will use to monitor Hadoop.
- Click Validate current document to check your configuration.
- Click Save current document to apply the changes.
These are the pre-configured samplers available to use in
Configure the required fields by referring to the table below:
HadoopMonitoring.xml template provides the variables that are set in the Environments section.
|HADOOP_HOST_NAMENODE||IP/Hostname where Namenode daemon is running.|
|HADOOP_HOST_SECONDARYNAMENODE||IP/Hostname where Secondarynamenode daemon is running.|
|HADOOP_HOST_DATANODE||IP/Hostname where the specific Datanode daemon is running.|
|HADOOP_HOST_RESOURCEMANAGER||IP/Hostname where ResourceManager is running.|
|HADOOP_PORT_JMX_NAMENODE||Namenode JMX port.|
|HADOOP_PORT_JMX_SECONDARYNAMENODE||Secondarynamenode JMX port.|
|HADOOP_PORT_WEBJMX_DATANODE||Datanode web UI port.
|HADOOP_PORT_JMX_RESOURCEMANAGER||ResourceManager JMX port|
|HADOOP_PORT_WEBJMX_NAMENODE||Namenode UI port .
|HADOOP_PORT_WEBJMX_RESOURCEMANAGER||ResourceManager web UI port.
|PYTHON_EXECUTABLE_PATH||Script that runs the Python program.|
HadoopMonitoring-SampleRules.xml template also provides a separate sample rules that you can use to configure the Gateway Setup Editor.
Your configuration rules must be set in the Includes section.
The table below shows the included rule setup in the configuration file:
|Hadoop-NameNodeCluster-Disk-Remaining||Checks the remaining disk ratio of the entire Hadoop cluster.|
|Hadoop-DataNode-Disk-Remaining||Checks the remaining disk ration of a single datanode
HADOOP_RULE_DISK_REMAINING_THRESHOLD: Possible values 1.0 - 100.
|Hadoop-Datanodes-In-Errors||Checks the number of nodes with errors
HADOOP_RULE_DATANODES_ERROR_THRESHOLD: Integer values.
|Hadoop-Blocks-In-Error||Checks the number of blocks with error
HADOOP_RULE_BLOCKS_ERROR_THRESHOLD: Integer values.
|Hadoop-Nodemanager-In-Error:||Checks the number of nodemanagers with error
HADOOP_RULE_NODEMANAGER_ERROR_THRESHOLD: Integer value.
|Hadoop-Applications-In-Error:||Checks the number of application with error
HADOOP_RULE_APPLICATION_ERROR_THRESHOLD: Integer values.
|Hadoop-SecondaryNamenode-Status :||Checks the connection status of JMX plugin to Secondarynamenode service.|
|Hadoop-NodeManager-State:||Checks the state of nodemanager
Note: The sample configuration file is verified to be working with Apache Hadoop 3.0.0, Python 2.7, and Netprobe 4.5 version.