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

Opportunistic containers in Hadoop 3.x


Containers are allocated to nodes by the scheduler only when there is sufficient unallocated resources at a node. YARN guarantees that once the application master dispatches a container to a node, the execution will immediately start. The execution of a container will only be completed if there is no violation of fairness or capacity, which means until some other containers ask for preemption of resources from the node, the container is guaranteed to run to completion.

The current container execution design allows an efficient task execution but it has two primary limitations, which are as follows:

  • Heartbeat delay: The Node Manager at regular intervals sends heartbeats to its resource manager and the heartbeat request also contains the resource metrics of a Node Manager. If any container running on a Node Manager finishes its execution then the information is sent as part of request in the next heartbeat, which means that the Resource Manager knows that...
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