<?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 Fair scheduler job submission concept in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Fair-scheduler-job-submission-concept/m-p/31734#M7273</link>
    <description>&lt;P&gt;Since reading several articles on fair scheduler, I am still at loss, if there are not preemptive stuff configured, and user A is looking for all the available resources and still needs more , and than user B, submits a job, would fair scheduler allow B to start obtaining containers as soon some containers are freed by A, Or B would wait for all the running and requested containers for B are done? Much appreciate the input, I wish I could mimic this but not able to so appreciate some insight.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Dev&lt;/P&gt;</description>
    <pubDate>Fri, 11 Sep 2015 14:41:20 GMT</pubDate>
    <dc:creator>Dev4Hadoop</dc:creator>
    <dc:date>2015-09-11T14:41:20Z</dc:date>
    <item>
      <title>Fair scheduler job submission concept</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Fair-scheduler-job-submission-concept/m-p/31734#M7273</link>
      <description>&lt;P&gt;Since reading several articles on fair scheduler, I am still at loss, if there are not preemptive stuff configured, and user A is looking for all the available resources and still needs more , and than user B, submits a job, would fair scheduler allow B to start obtaining containers as soon some containers are freed by A, Or B would wait for all the running and requested containers for B are done? Much appreciate the input, I wish I could mimic this but not able to so appreciate some insight.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Dev&lt;/P&gt;</description>
      <pubDate>Fri, 11 Sep 2015 14:41:20 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Fair-scheduler-job-submission-concept/m-p/31734#M7273</guid>
      <dc:creator>Dev4Hadoop</dc:creator>
      <dc:date>2015-09-11T14:41:20Z</dc:date>
    </item>
    <item>
      <title>Re: Fair scheduler job submission concept</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Fair-scheduler-job-submission-concept/m-p/32354#M7274</link>
      <description>Given a fully used situation with preemption disabled, B will begin running as soon as A's containers complete (as opposed to waiting the A application to end entirely before it runs).</description>
      <pubDate>Sun, 27 Sep 2015 14:51:10 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Fair-scheduler-job-submission-concept/m-p/32354#M7274</guid>
      <dc:creator>Harsh J</dc:creator>
      <dc:date>2015-09-27T14:51:10Z</dc:date>
    </item>
    <item>
      <title>Re: Fair scheduler job submission concept</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Fair-scheduler-job-submission-concept/m-p/32376#M7275</link>
      <description>&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Sun, 27 Sep 2015 23:52:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Fair-scheduler-job-submission-concept/m-p/32376#M7275</guid>
      <dc:creator>Dev4Hadoop</dc:creator>
      <dc:date>2015-09-27T23:52:04Z</dc:date>
    </item>
  </channel>
</rss>

