5.4. MapReduce2 Alerts (Hadoop 2 only)
Sidebar
Prev
|
Up
|
Next
Docs
Hortonworks Data Platform
5.4. MapReduce2 Alerts (Hadoop 2 only)
These alerts are used to monitor MR2.
Legal notices
Contents
Search
1. Introducing Ambari Web
1. Architecture
1.1. Sessions
2. Starting and Accessing Ambari Web
2. Monitoring and Managing HDP Clusters Using Ambari Web
1. Viewing Metrics on the Dashboard
1.1. Scanning System Metrics
1.1.1. Drilling Into Metrics for a Service
1.1.2. Viewing Cluster-Wide Metrics
1.1.3. Adding a Widget to the Dashboard
1.1.4. Resetting the Dashboard
1.1.5. Viewing Metrics in Ganglia
1.1.6. Customizing Metrics Display
1.1.7. Viewing More Metrics for your HDP Stack
1.2. Viewing Heatmaps
1.3. Scanning Services Status
2. Monitoring and Managing Services
2.1. Starting and Stopping All Services
2.2. Selecting a Service
2.2.1. Adding a Service
2.2.1.1. Adding a Service to your Hadoop cluster
2.3. Viewing Summary, Alert, and Health Information
2.3.1. Alerts and Health Checks
2.4. Configuring Services
2.4.1. Updating Service Properties
2.4.2. Customizing Logging Properties
2.4.3. Managing Configuration Groups
2.4.4. Restarting components
2.4.5. Performing Service Actions
2.4.6. Rolling Restarts
2.4.6.1. Setting Rolling Restart Parameters
2.4.6.2. Aborting a Rolling Restart
2.4.7. Monitoring Background Operations
2.4.8. Using Quick Links
2.4.9. Analyzing Service Metrics
3. Managing Hosts
3.1. Working with Hosts
3.2. Determining Host Status
3.3. Filtering the Hosts List
3.4. Performing Host-Level Actions
3.5. Viewing Components on a Host
3.6. Decommissioning Masters and Slaves
3.6.1. How to Decommission a Component
3.6.2. How to Delete a Component
3.7. Deleting a Host from a Cluster
3.7.1. How to Delete a Host from a Cluster
3.8. Setting Maintenance Mode
3.8.1. Setting Maintenance Mode for Services, Components, and Hosts
3.8.1.1. How to Turn On Maintenance Mode for a Service
3.8.1.2. How to Turn On Maintenance Mode for a Host
3.8.1.3. How to Turn On Maintenance Mode for a Host (alternative using filtering for hosts)
3.8.1.4. Maintenance Mode Use Cases
3.9. Adding Hosts to a Cluster
4. Administering Ambari
4.1. Managing Ambari Web Users
4.2. Enabling High Availability of HDP Components
4.3. Enabling Kerberos Security
4.4. Checking Stack and Component Versions
4.5. Managing Stack Repositories
4.5.1. Viewing a Stack Repository URL
4.5.2. Modifying Stack Repository URL
4.6. Checking Service User Accounts and Groups
4.7. Accessing Jobs Monitoring Information
4.7.1. Disabling the Jobs View
4.7.2. Disabling the YARN Timeline Service
3. Using Nagios With Hadoop
1. Basic Nagios Architecture
2. Installing Nagios
3. Configuration File Locations
4. Configuring Nagios Alerts For Hadoop Services
5. Nagios Alerts For Hadoop Services
5.1. HDFS Service Alerts
5.1.1. Blocks health
5.1.1.1. Potential causes
5.1.1.2. Possible remedies
5.1.2. NameNode process
5.1.2.1. Potential causes
5.1.2.2. Possible remedies
5.1.3. DataNode space
5.1.3.1. Potential causes
5.1.3.2. Possible remedies
5.1.4. DataNode process
5.1.4.1. Potential causes
5.1.4.2. Possible remedies
5.1.5. NameNode host CPU utilization
5.1.5.1. Potential causes
5.1.5.2. Possible remedies
5.1.6. NameNode edit logs directory status
5.1.6.1. Potential causes
5.1.6.2. Possible remedies
5.1.7. NameNode Web UI
5.1.7.1. Potential causes
5.1.7.2. Possible remedies
5.1.8. Percent DataNodes with space available
5.1.8.1. Potential causes
5.1.8.2. Possible remedies
5.1.9. Percent DataNodes live
5.1.9.1. Potential causes
5.1.9.2. Possible remedies
5.1.10. NameNode RPC latency
5.1.10.1. Potential causes
5.1.10.2. Possible remedies
5.1.11. HDFS capacity utilization
5.1.11.1. Potential causes
5.1.11.2. Possible remedies
5.2. NameNode HA Alerts (Hadoop 2 only)
5.2.1. JournalNode process
5.2.1.1. Potential causes
5.2.1.2. Possible remedies
5.2.2. NameNode HA Healthy process
5.2.2.1. Potential causes
5.2.2.2. Possible remedies
5.3. YARN Alerts (Hadoop 2 only)
5.3.1. ResourceManager process
5.3.1.1. Potential causes
5.3.1.2. Possible remedies
5.3.2. Percent NodeManagers live
5.3.2.1. Potential causes
5.3.2.2. Possible remedies
5.3.3. ResourceManager Web UI
5.3.3.1. Potential causes
5.3.3.2. Possible remedies
5.3.4. ResourceManager RPC latency
5.3.4.1. Potential causes
5.3.4.2. Possible remedies
5.3.5. ResourceManager CPU utilization
5.3.5.1. Potential causes
5.3.5.2. Possible remedies
5.3.6. NodeManager process
5.3.6.1. Potential causes
5.3.6.2. Possible remedies
5.3.7. NodeManager health
5.3.7.1. Potential causes
5.3.7.2. Possible remedies
5.4. MapReduce2 Alerts (Hadoop 2 only)
5.4.1. HistoryServer Web UI
5.4.1.1. Potential causes
5.4.1.2. Possible remedies
5.4.2. HistoryServer RPC latency
5.4.2.1. Potential causes
5.4.2.2. Possible remedies
5.4.3. HistoryServer CPU utilization
5.4.3.1. Potential causes
5.4.3.2. Possible remedies
5.4.4. HistoryServer process
5.4.4.1. Potential causes
5.4.4.2. Possible remedies
5.5. MapReduce Service Alerts (Hadoop 1 only)
5.5.1. JobTracker RPC latency alert
5.5.1.1. Potential causes
5.5.1.2. Possible remedies
5.5.2. JobTracker process
5.5.2.1. Potential causes
5.5.2.2. Possible remedies
5.5.3. JobTracker Web UI
5.5.3.1. Potential causes
5.5.3.2. Possible remedies
5.5.4. JobTracker CPU utilization
5.5.4.1. Potential causes
5.5.4.2. Possible remedies
5.5.5. HistoryServer Web UI
5.5.5.1. Potential causes
5.5.5.2. Possible remedies
5.5.6. HistoryServer process
5.5.6.1. Potential causes
5.5.6.2. Possible remedies
5.6. HBase Service Alerts
5.6.1. Percent RegionServers live
5.6.1.1. Potential causes
5.6.1.2. Possible remedies
5.6.2. HBase Master process
5.6.2.1. Potential causes
5.6.2.2. Possible remedies
5.6.3. HBase Master Web UI
5.6.3.1. Potential causes
5.6.3.2. Possible remedies
5.6.4. HBase Master CPU utilization
5.6.4.1. Potential causes
5.6.4.2. Possible remedies
5.6.5. RegionServer process
5.6.5.1. Potential causes
5.6.5.2. Possible remedies
5.7. Hive Alerts
5.7.1. Hive-Metastore status
5.7.1.1. Potential causes
5.7.1.2. Possible remedies
5.8. WebHCat Alerts
5.8.1. WebHCat Server status
5.8.1.1. Potential causes
5.8.1.2. Possible remedies
5.9. Oozie Alerts
5.9.1. Oozie status
5.9.1.1. Potential causes
5.9.1.2. Possible remedies
5.10. Ganglia Alerts
5.10.1. Ganglia Server status
5.10.1.1. Potential causes
5.10.1.2. Possible remedies
5.10.2. Ganglia Monitor process
5.10.2.1. Potential causes
5.10.2.2. Possible remedies
5.11. Nagios Alerts
5.11.1. Nagios status log freshness
5.11.1.1. Potential causes
5.11.1.2. Possible remedies
5.12. ZooKeeper Alerts
5.12.1. Percent ZooKeeper servers live
5.12.1.1. Potential causes
5.12.1.2. Possible remedies
5.12.2. Zookeeper Server process
5.12.2.1. Potential causes
5.12.2.2. Possible remedies
5.13. Ambari Alerts
5.13.1. Ambari Agent process.
5.13.1.1. Potential causes
5.13.1.2. Possible remedies
Search
Search Highlighter (On/Off)
