<?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: How can we isolate the jobs running in the same queue? in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/How-can-we-isolate-the-jobs-running-in-the-same-queue/m-p/119555#M82333</link>
    <description>&lt;P&gt;take a look at job &lt;A href="http://hortonworks.com/blog/better-slas-via-resource-preemption-in-yarns-capacityscheduler/"&gt;preemption&lt;/A&gt;, new feature in YARN. &lt;A rel="user" href="https://community.cloudera.com/users/1966/prasad4ucom.html" nodeid="1966"&gt;@Ram D&lt;/A&gt; you can also raise and lower the &lt;A href="https://hadoop.apache.org/docs/current/hadoop-mapreduce-client/hadoop-mapreduce-client-core/MapredCommands.html"&gt;priority&lt;/A&gt; of each job.&lt;/P&gt;&lt;P&gt;Command to interact with Map Reduce Jobs.&lt;/P&gt;&lt;P&gt;Usage: hadoop job [GENERIC_OPTIONS] [-submit &amp;lt;job-file&amp;gt;] | [-status &amp;lt;job-id&amp;gt;] | [-counter &amp;lt;job-id&amp;gt; &amp;lt;group-name&amp;gt; &amp;lt;counter-name&amp;gt;] | [-kill &amp;lt;job-id&amp;gt;] | [-events &amp;lt;job-id&amp;gt; &amp;lt;from-event-#&amp;gt; &amp;lt;#-of-events&amp;gt;] | [-history [all] &amp;lt;jobOutputDir&amp;gt;] | [-list [all]] | [-kill-task &amp;lt;task-id&amp;gt;] | [-fail-task &amp;lt;task-id&amp;gt;] | [-set-priority &amp;lt;job-id&amp;gt; &amp;lt;priority&amp;gt;]&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH&gt;COMMAND_OPTION&lt;/TH&gt;&lt;TH&gt;Description&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-submit &lt;EM&gt;job-file&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Submits the job.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-status &lt;EM&gt;job-id&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Prints the map and reduce completion percentage and all job counters.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-counter &lt;EM&gt;job-id&lt;/EM&gt; &lt;EM&gt;group-name&lt;/EM&gt; &lt;EM&gt;counter-name&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Prints the counter value.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-kill &lt;EM&gt;job-id&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Kills the job.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-events &lt;EM&gt;job-id&lt;/EM&gt; &lt;EM&gt;from-event-#&lt;/EM&gt; &lt;EM&gt;#-of-events&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Prints the events' details received by jobtracker for the given range.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-history [all]&lt;EM&gt;jobOutputDir&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Prints job details, failed and killed tip details. More details about the job such as successful tasks and task attempts made for each task can be viewed by specifying the [all] option.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-list [all]&lt;/TD&gt;&lt;TD&gt;Displays jobs which are yet to complete. -list all displays all jobs.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-kill-task &lt;EM&gt;task-id&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Kills the task. Killed tasks are NOT counted against failed attempts.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-fail-task &lt;EM&gt;task-id&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Fails the task. Failed tasks are counted against failed attempts.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;-set-priority &lt;EM&gt;job-id&lt;/EM&gt; &lt;EM&gt;priority&lt;/EM&gt;&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;&lt;STRONG&gt;Changes the priority of the job. Allowed priority values are VERY_HIGH, HIGH, NORMAL, LOW, VERY_LOW&lt;/STRONG&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
    <pubDate>Mon, 01 Feb 2016 22:23:25 GMT</pubDate>
    <dc:creator>aervits</dc:creator>
    <dc:date>2016-02-01T22:23:25Z</dc:date>
    <item>
      <title>How can we isolate the jobs running in the same queue?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/How-can-we-isolate-the-jobs-running-in-the-same-queue/m-p/119554#M82332</link>
      <description>&lt;P&gt;I created four node labels, assigned 4 nodes to each node label. Now, the jobs are running fine in the specified queues and on assigned nodes through node labels. Let us consider a case, two jobs are running in the same queue. Does one job which is acquiring more cluster resources will kill another job in the same queue? How can we isolate two jobs without impacting each other? Is there any solution?&lt;/P&gt;</description>
      <pubDate>Mon, 01 Feb 2016 22:20:54 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/How-can-we-isolate-the-jobs-running-in-the-same-queue/m-p/119554#M82332</guid>
      <dc:creator>prasad4u_com</dc:creator>
      <dc:date>2016-02-01T22:20:54Z</dc:date>
    </item>
    <item>
      <title>Re: How can we isolate the jobs running in the same queue?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/How-can-we-isolate-the-jobs-running-in-the-same-queue/m-p/119555#M82333</link>
      <description>&lt;P&gt;take a look at job &lt;A href="http://hortonworks.com/blog/better-slas-via-resource-preemption-in-yarns-capacityscheduler/"&gt;preemption&lt;/A&gt;, new feature in YARN. &lt;A rel="user" href="https://community.cloudera.com/users/1966/prasad4ucom.html" nodeid="1966"&gt;@Ram D&lt;/A&gt; you can also raise and lower the &lt;A href="https://hadoop.apache.org/docs/current/hadoop-mapreduce-client/hadoop-mapreduce-client-core/MapredCommands.html"&gt;priority&lt;/A&gt; of each job.&lt;/P&gt;&lt;P&gt;Command to interact with Map Reduce Jobs.&lt;/P&gt;&lt;P&gt;Usage: hadoop job [GENERIC_OPTIONS] [-submit &amp;lt;job-file&amp;gt;] | [-status &amp;lt;job-id&amp;gt;] | [-counter &amp;lt;job-id&amp;gt; &amp;lt;group-name&amp;gt; &amp;lt;counter-name&amp;gt;] | [-kill &amp;lt;job-id&amp;gt;] | [-events &amp;lt;job-id&amp;gt; &amp;lt;from-event-#&amp;gt; &amp;lt;#-of-events&amp;gt;] | [-history [all] &amp;lt;jobOutputDir&amp;gt;] | [-list [all]] | [-kill-task &amp;lt;task-id&amp;gt;] | [-fail-task &amp;lt;task-id&amp;gt;] | [-set-priority &amp;lt;job-id&amp;gt; &amp;lt;priority&amp;gt;]&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH&gt;COMMAND_OPTION&lt;/TH&gt;&lt;TH&gt;Description&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-submit &lt;EM&gt;job-file&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Submits the job.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-status &lt;EM&gt;job-id&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Prints the map and reduce completion percentage and all job counters.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-counter &lt;EM&gt;job-id&lt;/EM&gt; &lt;EM&gt;group-name&lt;/EM&gt; &lt;EM&gt;counter-name&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Prints the counter value.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-kill &lt;EM&gt;job-id&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Kills the job.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-events &lt;EM&gt;job-id&lt;/EM&gt; &lt;EM&gt;from-event-#&lt;/EM&gt; &lt;EM&gt;#-of-events&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Prints the events' details received by jobtracker for the given range.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-history [all]&lt;EM&gt;jobOutputDir&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Prints job details, failed and killed tip details. More details about the job such as successful tasks and task attempts made for each task can be viewed by specifying the [all] option.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-list [all]&lt;/TD&gt;&lt;TD&gt;Displays jobs which are yet to complete. -list all displays all jobs.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-kill-task &lt;EM&gt;task-id&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Kills the task. Killed tasks are NOT counted against failed attempts.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;-fail-task &lt;EM&gt;task-id&lt;/EM&gt;&lt;/TD&gt;&lt;TD&gt;Fails the task. Failed tasks are counted against failed attempts.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;STRONG&gt;-set-priority &lt;EM&gt;job-id&lt;/EM&gt; &lt;EM&gt;priority&lt;/EM&gt;&lt;/STRONG&gt;&lt;/TD&gt;&lt;TD&gt;&lt;STRONG&gt;Changes the priority of the job. Allowed priority values are VERY_HIGH, HIGH, NORMAL, LOW, VERY_LOW&lt;/STRONG&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Mon, 01 Feb 2016 22:23:25 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/How-can-we-isolate-the-jobs-running-in-the-same-queue/m-p/119555#M82333</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-02-01T22:23:25Z</dc:date>
    </item>
    <item>
      <title>Re: How can we isolate the jobs running in the same queue?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/How-can-we-isolate-the-jobs-running-in-the-same-queue/m-p/119556#M82334</link>
      <description>&lt;P&gt;How can we isolate two jobs without impacting each other? My requirement is jobs must be run wihtout impacting each other in the same queue. By setting same priority to both jobs is the solution ? &lt;/P&gt;</description>
      <pubDate>Mon, 01 Feb 2016 22:36:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/How-can-we-isolate-the-jobs-running-in-the-same-queue/m-p/119556#M82334</guid>
      <dc:creator>prasad4u_com</dc:creator>
      <dc:date>2016-02-01T22:36:37Z</dc:date>
    </item>
    <item>
      <title>Re: How can we isolate the jobs running in the same queue?</title>
      <link>https://community.cloudera.com/t5/Support-Questions/How-can-we-isolate-the-jobs-running-in-the-same-queue/m-p/119557#M82335</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1966/prasad4ucom.html" nodeid="1966"&gt;@Ram D&lt;/A&gt; &lt;STRONG&gt;Changes the priority of the job. Allowed priority values are VERY_HIGH, HIGH, NORMAL, LOW, VERY_LOW. Change one job's priority from NORMAL and it will work. You can also look at preemption.&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Feb 2016 22:38:43 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/How-can-we-isolate-the-jobs-running-in-the-same-queue/m-p/119557#M82335</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-02-01T22:38:43Z</dc:date>
    </item>
  </channel>
</rss>

