<?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: JOB Stuck in Accepted State in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/JOB-Stuck-in-Accepted-State/m-p/30267#M34273</link>
    <description>&lt;P&gt;What the FS takes into account depends on the scheduling type that you have chosen: DRF, Fair or FIFO. Default is DRF which takes into account both memory and CPU.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;An application that asks for more resources than the cluster can accommodate, i.e I request 100GB for a container and the maximum container can only be 64GB then it will be rejected. However if I ask for 32 GB and the maximum container is 64GB but there is no node that is large enough to handle the 32 GB then it will just sit there forever (YARN-56). If the maximum container size is 64GB but no node can&amp;nbsp;accommodate that container it most likely will just sit there too.&lt;/P&gt;&lt;P&gt;I am not sure what would happen if I request a 32GB container for a queue which has only 16GB as the maximum resources if it will be rejected or just sit there forever. I have not tested that case.&lt;/P&gt;&lt;P&gt;So you might have a misconfiguration or just run into a bug.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;BTW: whatever was mentioned for memory is true for vcores also.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wilfred&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jul 2015 07:11:02 GMT</pubDate>
    <dc:creator>Wilfred</dc:creator>
    <dc:date>2015-07-30T07:11:02Z</dc:date>
  </channel>
</rss>

