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

Namenode HA using shared storage


In Hadoop, we do not recommend NAS or SAN as storage for Datanodes, as it defeats the purpose of localized data. However, for critical components such as Namenode, there will be a storage mount point to store Namenode metadata. This is specified as a comma-separated list under the dfs.namenode.name.dir parameter.

For Namenode High Availability (HA), we need a shared location to store metadata, which can be accessed from both Namenodes. Only primary or active Namenodes can write to the shared location, but both Namenodes can read from it.

The active Namenode is the writer and the standby node is the reader node only. Namenode can failover from one node to another, but only one node can be Active at any given time. Another important thing to keep in mind is that the Datanodes talk to both the Namenodes so that after failure between Namenodes, there is no time taken to update the block report.

The shared storage can be any NFS server or a simple filer that can...