Book Image

Hadoop 2.x Administration Cookbook

By : Aman Singh
Book Image

Hadoop 2.x Administration Cookbook

By: Aman Singh

Overview of this book

Hadoop enables the distributed storage and processing of large datasets across clusters of computers. Learning how to administer Hadoop is crucial to exploit its unique features. With this book, you will be able to overcome common problems encountered in Hadoop administration. The book begins with laying the foundation by showing you the steps needed to set up a Hadoop cluster and its various nodes. You will get a better understanding of how to maintain Hadoop cluster, especially on the HDFS layer and using YARN and MapReduce. Further on, you will explore durability and high availability of a Hadoop cluster. You’ll get a better understanding of the schedulers in Hadoop and how to configure and use them for your tasks. You will also get hands-on experience with the backup and recovery options and the performance tuning aspects of Hadoop. Finally, you will get a better understanding of troubleshooting, diagnostics, and best practices in Hadoop administration. By the end of this book, you will have a proper understanding of working with Hadoop clusters and will also be able to secure, encrypt it, and configure auditing for your Hadoop clusters.
Table of Contents (20 chapters)
Hadoop 2.x Administration Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface
Index

Resourcemanager troubleshooting


In this recipe, we will look at common Resourcemanager issues and how these can be addressed.

Getting ready

To step through the recipe in this section, make sure the users have completed the Setting up multi-node HBase cluster recipe in Chapter 9, HBase Administration.

How to do it…

Scenario 1: Resourcemanager daemon not starting.

  1. The Resourcemanager, by default, will bind to port 80030 to 80033 and 8088. These ports can be configured in the yarn-site.xml file and you should make sure these are unique and not used by any other service. In our labs, we used the ports as shown in the following screenshot:

  2. The listening ports can be seen by using the following command:

    $ netsta -tlpn
    
  3. Look into the logs for any Bind Errors and make sure the hostname is resolvable. Check for both forward and reverse lookup:

    $ nslookup <resource_manager_host>
    
  4. On Node Manager, the import ports are 8040, 8041, and 8042. These are used for scheduling, localization, and so on. So,...