<?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: Round Robin Queuing in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Round-Robin-Queuing/m-p/142471#M19602</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1486/smanjee.html" nodeid="1486"&gt;@Sunile Manjee&lt;/A&gt;this is an educated guess but we're talking about YARN queues with RoundRobin schedule implementation. So instead of capacity scheduler we would implement another scheduler algorithm. I don't think it's viable unless cluster only dedicated to hive it would be cool to try having two root queues supporting multiple schedulers. &lt;A href="http://m.linuxjournal.com/content/how-yarn-changed-hadoop-job-scheduling" target="_blank"&gt;http://m.linuxjournal.com/content/how-yarn-changed-hadoop-job-scheduling&lt;/A&gt;&lt;/P&gt;&lt;P&gt;So with that idea in mind you world assign an available queue in round robin fashion to each user.&lt;/P&gt;</description>
    <pubDate>Tue, 16 Feb 2016 19:19:10 GMT</pubDate>
    <dc:creator>aervits</dc:creator>
    <dc:date>2016-02-16T19:19:10Z</dc:date>
    <item>
      <title>Round Robin Queuing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Round-Robin-Queuing/m-p/142470#M19601</link>
      <description>&lt;P&gt;
	I read in this tutorial &lt;A href="http://hortonworks.com/hadoop-tutorial/supercharging-interactive-queries-hive-tez/" target="_blank"&gt;http://hortonworks.com/hadoop-tutorial/supercharging-interactive-queries-hive-tez/&lt;/A&gt;  about&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Multi-tenancy with HiveServer2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;
	There could be contentions when multiple users run large queries simultaneously. Processing queries with many containers could lead to lower latency. For this, 3 controls could be put in place:&lt;/P&gt;&lt;UL&gt;
	
&lt;LI&gt;Container re-use timeout&lt;/LI&gt;	
&lt;LI&gt;Tez split wave tuning&lt;/LI&gt;	
&lt;LI&gt;Round Robin Queuing setup&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;
	What is Round Robin Queuing Setup within Hive/Tez?  How would one go about the setup?  No details were provided.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Feb 2016 11:52:31 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Round-Robin-Queuing/m-p/142470#M19601</guid>
      <dc:creator>sunile_manjee</dc:creator>
      <dc:date>2016-02-16T11:52:31Z</dc:date>
    </item>
    <item>
      <title>Re: Round Robin Queuing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Round-Robin-Queuing/m-p/142471#M19602</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1486/smanjee.html" nodeid="1486"&gt;@Sunile Manjee&lt;/A&gt;this is an educated guess but we're talking about YARN queues with RoundRobin schedule implementation. So instead of capacity scheduler we would implement another scheduler algorithm. I don't think it's viable unless cluster only dedicated to hive it would be cool to try having two root queues supporting multiple schedulers. &lt;A href="http://m.linuxjournal.com/content/how-yarn-changed-hadoop-job-scheduling" target="_blank"&gt;http://m.linuxjournal.com/content/how-yarn-changed-hadoop-job-scheduling&lt;/A&gt;&lt;/P&gt;&lt;P&gt;So with that idea in mind you world assign an available queue in round robin fashion to each user.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Feb 2016 19:19:10 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Round-Robin-Queuing/m-p/142471#M19602</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-02-16T19:19:10Z</dc:date>
    </item>
    <item>
      <title>Re: Round Robin Queuing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Round-Robin-Queuing/m-p/142472#M19603</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/1486/smanjee.html" nodeid="1486"&gt;@Sunile Manjee&lt;/A&gt;&lt;P&gt;This is related to connection to HS2 in round robin when we have multiple HS2 running and we don't want to hit the same HS2 instance. &lt;A target="_blank" href="https://www.pythian.com/blog/setup-high-availability-load-balancing-hiveserver2/"&gt;Link&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The whole concept is derived from basic &lt;A target="_blank" href="https://en.wikipedia.org/wiki/Round-robin_scheduling"&gt;Round Robin &lt;/A&gt; algorithm&lt;/P&gt;&lt;P&gt;This leverages the Zookeeper&lt;/P&gt;</description>
      <pubDate>Tue, 16 Feb 2016 19:30:43 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Round-Robin-Queuing/m-p/142472#M19603</guid>
      <dc:creator>nsabharwal</dc:creator>
      <dc:date>2016-02-16T19:30:43Z</dc:date>
    </item>
    <item>
      <title>Re: Round Robin Queuing</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Round-Robin-Queuing/m-p/142473#M19604</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1486/smanjee.html" nodeid="1486"&gt;@Sunile Manjee&lt;/A&gt;  See this thread on HS2 and ZK relationship &lt;A href="https://community.hortonworks.com/questions/1342/how-to-enable-zookeeper-discovery-for-hiveserver2.html"&gt;https://community.hortonworks.com/questions/1342/how-to-enable-zookeeper-discovery-for-hiveserver2.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Feb 2016 19:31:58 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Round-Robin-Queuing/m-p/142473#M19604</guid>
      <dc:creator>nsabharwal</dc:creator>
      <dc:date>2016-02-16T19:31:58Z</dc:date>
    </item>
  </channel>
</rss>

