<?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: Invalid resource request, requested resource type=[yarn.io/gpu] in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Invalid-resource-request-requested-resource-type-yarn-io-gpu/m-p/243628#M205426</link>
    <description>&lt;P&gt;It seems to be about the ResourceCalculator used when requesting containers, as it shows only CPU/memory, like the DefaultResourceCalculator should do it. But Everywhere I check, my node registers his GPU properly and DominantResourceCalculator is set...&lt;/P&gt;</description>
    <pubDate>Fri, 08 Feb 2019 23:25:35 GMT</pubDate>
    <dc:creator>azoulay_kevin</dc:creator>
    <dc:date>2019-02-08T23:25:35Z</dc:date>
    <item>
      <title>Invalid resource request, requested resource type=[yarn.io/gpu]</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Invalid-resource-request-requested-resource-type-yarn-io-gpu/m-p/243626#M205424</link>
      <description>&lt;P&gt;I'm facing this issue when try to using GPU on YARN:&lt;/P&gt;&lt;PRE&gt;Caused by: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.yarn.exceptions.InvalidResourceRequestException): Invalid resource request, requested resource type=[yarn.io/gpu] &amp;lt; 0 or greater than maximum allowed allocation. Requested resource=&amp;lt;memory:3072, vCores:1, yarn.io/gpu: 1&amp;gt;, maximum allowed allocation=&amp;lt;memory:9216, vCores:9&amp;gt;, please note that maximum allowed allocation is calculated by scheduler based on maximum resource of registered NodeManagers, which might be less than configured maximum allocation=&amp;lt;memory:9216, vCores:9, yarn.io/gpu: 9223372036854775807&amp;gt;&lt;/PRE&gt;&lt;P&gt;I already enabled GPU on my cluster but some how, it still showing that the (without yarn.io/gpu) maximum allowed allocation=&amp;lt;memory:9216, vCores:9&amp;gt;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jan 2019 23:31:07 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Invalid-resource-request-requested-resource-type-yarn-io-gpu/m-p/243626#M205424</guid>
      <dc:creator>vietanh_nguyen_</dc:creator>
      <dc:date>2019-01-31T23:31:07Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid resource request, requested resource type=[yarn.io/gpu]</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Invalid-resource-request-requested-resource-type-yarn-io-gpu/m-p/243627#M205425</link>
      <description>&lt;P&gt;Same exact problem. I have 2 GPUs in my test cluster, both are showing up (load included) in the RM / Nodes UI, but none of then can be allocated.... same "maximum allocation" reffering only to CPUs and RAM&lt;/P&gt;</description>
      <pubDate>Tue, 05 Feb 2019 22:29:10 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Invalid-resource-request-requested-resource-type-yarn-io-gpu/m-p/243627#M205425</guid>
      <dc:creator>azoulay_kevin</dc:creator>
      <dc:date>2019-02-05T22:29:10Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid resource request, requested resource type=[yarn.io/gpu]</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Invalid-resource-request-requested-resource-type-yarn-io-gpu/m-p/243628#M205426</link>
      <description>&lt;P&gt;It seems to be about the ResourceCalculator used when requesting containers, as it shows only CPU/memory, like the DefaultResourceCalculator should do it. But Everywhere I check, my node registers his GPU properly and DominantResourceCalculator is set...&lt;/P&gt;</description>
      <pubDate>Fri, 08 Feb 2019 23:25:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Invalid-resource-request-requested-resource-type-yarn-io-gpu/m-p/243628#M205426</guid>
      <dc:creator>azoulay_kevin</dc:creator>
      <dc:date>2019-02-08T23:25:35Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid resource request, requested resource type=[yarn.io/gpu]</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Invalid-resource-request-requested-resource-type-yarn-io-gpu/m-p/243629#M205427</link>
      <description>&lt;P&gt;After about 2 weeks of various tries we finally settled on a full wipe of every host for a clean install from scratch.&lt;BR /&gt;Still nothing working.&lt;BR /&gt;&lt;BR /&gt;Then we tried a "one worker" setup to set a countable resource manually to try the allocation mechanism and then....&lt;BR /&gt;NOTHING &lt;EM&gt;horton&lt;/EM&gt;WORKS !&lt;BR /&gt;&lt;BR /&gt;But my Googling was better suited then.&lt;BR /&gt;It seems to be a Hadoop related issue about custom resources and CapacityScheduler, enjoy:&lt;/P&gt;&lt;P&gt;&lt;A href="https://issues.apache.org/jira/browse/YARN-9161"&gt;https://issues.apache.org/jira/browse/YARN-9161&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://issues.apache.org/jira/browse/YARN-9205"&gt;https://issues.apache.org/jira/browse/YARN-9205&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Temporary solution to benefit from isolation:&lt;/P&gt;&lt;P&gt;For now (3.1.1/3.2.0) the capacity.CapacityScheduler is broken by a hardcoded enum containing only vCores and RAM parameters. You just have to switch your scheduler class to org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler You also want to replace "capacity" by "Fair" in the line yarn.scheduler.fair.resource-calculator=org.apache.hadoop.yarn.util.resource.DominantResourceCalculator&lt;/P&gt;&lt;P&gt;Your GPUs will not be visible on yarn ui2 but will still be on the NodeManagers, and most importantly, will be allocated properly. It was a mess to find out indeed.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2019 00:12:15 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Invalid-resource-request-requested-resource-type-yarn-io-gpu/m-p/243629#M205427</guid>
      <dc:creator>azoulay_kevin</dc:creator>
      <dc:date>2019-02-15T00:12:15Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid resource request, requested resource type=[yarn.io/gpu]</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Invalid-resource-request-requested-resource-type-yarn-io-gpu/m-p/243630#M205428</link>
      <description>&lt;P&gt;Have run into the same issue. It works with FairScheduler but not CapacityScheduler. To add to the instructions above for those who normally use CapacityScheduler (99.99% of the Hadoop population :-)) but want to try with FairScheduler, remember also to disable other CS specific features, such as Preemption as Resource Manager won't start otherwise.&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2019 15:34:14 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Invalid-resource-request-requested-resource-type-yarn-io-gpu/m-p/243630#M205428</guid>
      <dc:creator>aromero</dc:creator>
      <dc:date>2019-05-09T15:34:14Z</dc:date>
    </item>
  </channel>
</rss>

