<?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 How can we avoid Resource Manager to retry failed Application Master on the same NodeManager? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-can-we-avoid-Resource-Manager-to-retry-failed/m-p/52608#M58010</link>
    <description>&lt;P&gt;Can we avoid Resource Manager to retry failed Application Master on the same NodeManager? My hive job tried to lauch application master in same NM after multiple fails, It leads whole job fail after 4 retries.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 16 Sep 2022 11:19:28 GMT</pubDate>
    <dc:creator>stsudhakara</dc:creator>
    <dc:date>2022-09-16T11:19:28Z</dc:date>
    <item>
      <title>How can we avoid Resource Manager to retry failed Application Master on the same NodeManager?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-can-we-avoid-Resource-Manager-to-retry-failed/m-p/52608#M58010</link>
      <description>&lt;P&gt;Can we avoid Resource Manager to retry failed Application Master on the same NodeManager? My hive job tried to lauch application master in same NM after multiple fails, It leads whole job fail after 4 retries.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 11:19:28 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-can-we-avoid-Resource-Manager-to-retry-failed/m-p/52608#M58010</guid>
      <dc:creator>stsudhakara</dc:creator>
      <dc:date>2022-09-16T11:19:28Z</dc:date>
    </item>
    <item>
      <title>Re: How can we avoid Resource Manager to retry failed Application Master on the same NodeManager?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-can-we-avoid-Resource-Manager-to-retry-failed/m-p/52896#M58011</link>
      <description>&lt;P&gt;This response I got from the Cloudera support&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;"&lt;SPAN&gt;I can see you're running on CDH 5.3.3, and this was added as a feature in YARN-2005, which was included in CDH releases starting from CDH 5.5.0: "YARN-2005: Blacklisting support for scheduling AMs" &lt;A href="https://issues.apache.org/jira/browse/YARN-2005" target="_blank"&gt;https://issues.apache.org/jira/browse/YARN-2005&lt;/A&gt;,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Unfortunately this can't be backported to your version of CDH and you will have to resort to an upgrade "&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Another ticket related black listing AMs is&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://issues.apache.org/jira/browse/YARN-4389" target="_blank"&gt;https://issues.apache.org/jira/browse/YARN-4389&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This fix releasing with Hadoop&amp;nbsp;2.8.0.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 05:42:19 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-can-we-avoid-Resource-Manager-to-retry-failed/m-p/52896#M58011</guid>
      <dc:creator>stsudhakara</dc:creator>
      <dc:date>2017-03-30T05:42:19Z</dc:date>
    </item>
  </channel>
</rss>

