<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: relation between Resource Manager  and name node ? in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/relation-between-Resource-Manager-and-name-node/m-p/308589#M223627</link>
    <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/84211"&gt;@Chahat_0&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hadoop is designed to ensure that compute (Node Managers) runs as close to data (Data Nodes) as possible. Usually containers for jobs are allocated on the same nodes where the data is present. Hence in a typical Hadoop cluster, both Data Nodes and Node Manager run on the same machine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF6600"&gt;&lt;STRONG&gt;Node Manager&lt;/STRONG&gt;&lt;/FONT&gt;&amp;nbsp;is the RM slave process while the &lt;FONT color="#FF6600"&gt;Data Nodes&lt;/FONT&gt; is the Namenode slave process which&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;responsible for coordinating HDFS functions&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Resource Manager: Runs on a master daemon and manages the resource allocation in the cluster. Node Manager: They run on the slave daemons and are responsible for the execution of a task on every single Data Node&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Node Managers manage the containers requested by jobs&lt;BR /&gt;Data Nodes manage the data&lt;/LI&gt;&lt;LI&gt;The NodeManager (NM) is YARN’s per-node agent and takes care of the individual compute nodes in a Hadoop cluster. This includes keeping up-to-date with the ResourceManager (RM), overseeing containers’ life-cycle management; monitoring resource usage (memory, CPU) of individual containers, tracking node-health, log’s management, and auxiliary services that may be exploited by different YARN applications. NodeManager communicates directly with the ResourceManager.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Resource manager and Namenode both as master components [processes] that can run in single or HA setup should run on separate identical usually high spec servers [nodes] as compared to the data nodes. Zookeeper is another important component&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ResourceManager and NodeManager combine together to form a data-computation framework.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;FONT color="#FF6600"&gt;ResourceManager&lt;/FONT&gt; acts as the scheduler and allocates resources amongst all the applications in the system.&lt;/LI&gt;&lt;LI&gt;&lt;FONT color="#FF6600"&gt;NodeManager&lt;/FONT&gt; takes navigation from the ResourceManager and it runs on each node in the cluster. Resources available on a single node is managed by NodeManager.&lt;/LI&gt;&lt;LI&gt;&lt;FONT color="#FF6600"&gt;ApplicationMaster,&lt;/FONT&gt; a framework-specific library is responsible for running specific YARN job and for negotiating resources from the ResourceManager, and working with NodeManager to execute and monitor containers.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Hope that helps&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 03 Jan 2021 00:07:21 GMT</pubDate>
    <dc:creator>Shelton</dc:creator>
    <dc:date>2021-01-03T00:07:21Z</dc:date>
  </channel>
</rss>

