Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Hadoop 3

You're reading from  Mastering Hadoop 3

Product type Book
Published in Feb 2019
Publisher Packt
ISBN-13 9781788620444
Pages 544 pages
Edition 1st Edition
Languages
Authors (2):
Chanchal Singh Chanchal Singh
Profile icon Chanchal Singh
Manish Kumar Manish Kumar
Profile icon Manish Kumar
View More author details
Toc

Table of Contents (23) Chapters close

Title Page
Dedication
About Packt
Foreword
Contributors
Preface
1. Journey to Hadoop 3 2. Deep Dive into the Hadoop Distributed File System 3. YARN Resource Management in Hadoop 4. Internals of MapReduce 5. SQL on Hadoop 6. Real-Time Processing Engines 7. Widely Used Hadoop Ecosystem Components 8. Designing Applications in Hadoop 9. Real-Time Stream Processing in Hadoop 10. Machine Learning in Hadoop 11. Hadoop in the Cloud 12. Hadoop Cluster Profiling 13. Who Can Do What in Hadoop 14. Network and Data Security 15. Monitoring Hadoop 1. Other Books You May Enjoy Index

Quorum Journal Manager (QJM)


NameNode used to be a single point of failure before the release of Hadoop version 2. In Hadoop 1, each cluster consisted of a single NameNode. If this NameNode failed, then the entire cluster would be unavailable. So, until and unless the NameNode service restarted, no one could use the Hadoop cluster. In Hadoop 2, the high availability feature was introduced. It has two NameNodes, one of the NameNodes is in active state while the other NameNode is in standby state. The active NameNode serves the client requests while the standby NameNode maintains synchronization of its state to take over as the active NameNode if the current active NameNode fails. 

There is a Quorum Journal Manager (QJM) runs in each NameNode. The QJM is responsible for communicating with JournalNodes using RPC; for example, sending namespace modifications, that is, edits to JournalNodes, and so on. A JournalNode daemon can run on N machines where N is configurable. A QJM writes edits to the...

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 ₹800/month. Cancel anytime