Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning Hbase

You're reading from   Learning Hbase Learn the fundamentals of HBase administration and development with the help of real-time scenarios

Arrow left icon
Product type Paperback
Published in Nov 2014
Publisher
ISBN-13 9781783985944
Length 326 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Shashwat Shriparv Shashwat Shriparv
Author Profile Icon Shashwat Shriparv
Shashwat Shriparv
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Understanding the HBase Ecosystem FREE CHAPTER 2. Let's Begin with HBase 3. Let's Start Building It 4. Optimizing the HBase/Hadoop Cluster 5. The Storage, Structure Layout, and Data Model of HBase 6. HBase Cluster Maintenance and Troubleshooting 7. Scripting in HBase 8. Coding HBase in Java 9. Advance Coding in Java for HBase 10. HBase Use Cases Index

Hadoop optimization


If we have an optimized Hadoop cluster, a lot of problems are easily solved for other Hadoop ecosystem components on the cluster, for example HBase. So, now let's see some of the factors using which we can optimize Hadoop.

General optimization tips

These are some general optimization tips that will help us to optimize Hadoop:

  • Create a dedicated Hadoop/HBase user to run the daemons.

  • Try to use SSD for the NameNode metadata.

  • The NameNode metadata must be backed up periodically; it can be either on an hourly or daily basis. If it contains very valuable data, it must be backed up every 5 to 10 minutes. We can write crons to copy with the metadata directory.

  • We must have multiple metadata directories for NameNode, which can be specified using the parameters dfs.name.dir or dfs.namenode.name.dir; one can be located at local disk and another at network mount location (NFS). This provides redundancy of metadata, and robustness, in case of failure.

  • Set dfs.namenode.name.dir.restore to...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime