YARN goals aka why was Hadoop re-architected?
Resources
Great introduction
In depth posts

YARN goals aka why was Hadoop re-architected?
YARN, as an aspect of Hadoop, has two major kinds of benefits:
The ability to use programming frameworks other than MapReduce.
Scalability, no matter what programming framework you use.
The central goal of YARN is to clearly separate two things that are smushed together in current Hadoop, specifically in (mainly) JobTracker:
Monitoring the status of the cluster with respect to which nodes have which resources available. Under YARN, this will be global.
Managing the parallelization execution of any specific job. Under YARN, this will be done separately for each job.

Resources
Great introduction

In depth posts
http://hortonworks.com/blog/introducing-apache-hadoop-yarn/
http://hortonworks.com/blog/apache-hadoop-yarn-background-and-an-overview/
http://hortonworks.com/blog/apache-hadoop-yarn-concepts-and-applications/
http://hortonworks.com/blog/apache-hadoop-yarn-resourcemanager/
http://hortonworks.com/blog/apache-hadoop-yarn-nodemanager/
Videos
YARN: Hadoop beyond Map Reduce: http://www.youtube.com/watch?v=HHv2pkIJjR0

facebooktwittergoogle_plusredditlinkedinby feather

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>