<?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: Limit ressource allocate to HBase query based on user in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139702#M19325</link>
    <description>&lt;P&gt;Thanks for the fast reply guys! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 16 Feb 2016 17:49:43 GMT</pubDate>
    <dc:creator>michelsumbul</dc:creator>
    <dc:date>2016-02-16T17:49:43Z</dc:date>
    <item>
      <title>Limit ressource allocate to HBase query based on user</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139697#M19320</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Is there a way to specify how much ressource an user will be able to use for his HBase query?&lt;/P&gt;&lt;P&gt;The objectif is to be able to define group A that can use 40 % of the ressouce and group B 60%, thoses 2 groups have to query the same hbase cluster.&lt;/P&gt;&lt;P&gt;Some thing like we can do with the yarn queue manager but on every query lunch by every user?&lt;/P&gt;&lt;P&gt;Thanks for the info,&lt;/P&gt;&lt;P&gt;Michel&lt;/P&gt;</description>
      <pubDate>Fri, 12 Feb 2016 22:05:45 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139697#M19320</guid>
      <dc:creator>michelsumbul</dc:creator>
      <dc:date>2016-02-12T22:05:45Z</dc:date>
    </item>
    <item>
      <title>Re: Limit ressource allocate to HBase query based on user</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139698#M19321</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/1390/michelsumbul.html" nodeid="1390"&gt;@Michel Sumbul&lt;/A&gt;&lt;P&gt;Very good question...You may have to read this jira &lt;A href="https://issues.apache.org/jira/browse/HBASE-11598" target="_blank"&gt;https://issues.apache.org/jira/browse/HBASE-11598&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 12 Feb 2016 22:10:52 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139698#M19321</guid>
      <dc:creator>nsabharwal</dc:creator>
      <dc:date>2016-02-12T22:10:52Z</dc:date>
    </item>
    <item>
      <title>Re: Limit ressource allocate to HBase query based on user</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139699#M19322</link>
      <description>&lt;P&gt;Tagging experts &lt;A rel="user" href="https://community.cloudera.com/users/372/enis.html" nodeid="372"&gt;@Enis&lt;/A&gt; &lt;A rel="user" href="https://community.cloudera.com/users/223/jelser.html" nodeid="223"&gt;@Josh Elser&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Feb 2016 22:11:11 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139699#M19322</guid>
      <dc:creator>nsabharwal</dc:creator>
      <dc:date>2016-02-12T22:11:11Z</dc:date>
    </item>
    <item>
      <title>Re: Limit ressource allocate to HBase query based on user</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139700#M19323</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1390/michelsumbul.html" nodeid="1390"&gt;@Michel Sumbul&lt;/A&gt; the feature is called rquest throttling. It is available in HBase 1.1 and thus in HDP 2.3. More info &lt;A href="https://blogs.apache.org/hbase/entry/the_hbase_request_throttling_feature" target="_blank"&gt;https://blogs.apache.org/hbase/entry/the_hbase_request_throttling_feature&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The throttle can then be set from the HBase shell, like so:&lt;/P&gt;&lt;P&gt;hbase&amp;gt; set_quota TYPE =&amp;gt; THROTTLE, USER =&amp;gt; 'uname', LIMIT =&amp;gt; '100req/sec'&lt;/P&gt;&lt;P&gt;hbase&amp;gt; set_quota TYPE =&amp;gt; THROTTLE, TABLE =&amp;gt; 'tbl', LIMIT =&amp;gt; '10M/sec'&lt;/P&gt;&lt;P&gt;hbase&amp;gt; set_quota TYPE =&amp;gt; THROTTLE, NAMESPACE =&amp;gt; 'ns', LIMIT =&amp;gt; 'NONE'&lt;/P&gt;&lt;P&gt;our in-house engineer responded in a similar post recently &lt;A href="https://community.hortonworks.com/questions/1821/hbase-quota-management.html" target="_blank"&gt;https://community.hortonworks.com/questions/1821/hbase-quota-management.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Feb 2016 03:17:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139700#M19323</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-02-13T03:17:04Z</dc:date>
    </item>
    <item>
      <title>Re: Limit ressource allocate to HBase query based on user</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139701#M19324</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1390/michelsumbul.html" nodeid="1390"&gt;@Michel Sumbul&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The above jira provides the detail history on throttling.&lt;/P&gt;&lt;P&gt;Also, see if you can research on following parameter if you are using phoenix&lt;/P&gt;&lt;P&gt;phoenix.query.maxTenantMemoryPercentage&lt;/P&gt;&lt;P&gt;&lt;A href="https://phoenix.apache.org/tuning.html" target="_blank"&gt;https://phoenix.apache.org/tuning.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Feb 2016 03:27:23 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139701#M19324</guid>
      <dc:creator>nsabharwal</dc:creator>
      <dc:date>2016-02-13T03:27:23Z</dc:date>
    </item>
    <item>
      <title>Re: Limit ressource allocate to HBase query based on user</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139702#M19325</link>
      <description>&lt;P&gt;Thanks for the fast reply guys! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Feb 2016 17:49:43 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139702#M19325</guid>
      <dc:creator>michelsumbul</dc:creator>
      <dc:date>2016-02-16T17:49:43Z</dc:date>
    </item>
    <item>
      <title>Re: Limit ressource allocate to HBase query based on user</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139703#M19326</link>
      <description>&lt;P&gt;&lt;A href="https://community.hortonworks.com/questions/16632/limit-ressource-allocate-to-hbase-query-based-on-u.html#"&gt;@Artem Ervits&lt;/A&gt; &lt;A href="https://community.hortonworks.com/questions/16632/limit-ressource-allocate-to-hbase-query-based-on-u.html#"&gt;@Neeraj Sabharwal&lt;/A&gt; - I am trying to leverage size-based throttling but keep getting ThrottlingException when I start hbase, even when there is hardly any data in hbase. &lt;/P&gt;&lt;P&gt;I am sure this is some mis-configuration from my end but I cannot seem to find that out. Any inputs would be appreciated. Just to also add there is some correlation here between number of pre-splits and throttling size limit because the error shows up only when number of pre-splits are more. 
&lt;/P&gt;&lt;P&gt;Details : Hbase version : &lt;STRONG&gt;1.1.2&lt;/STRONG&gt;, Number of region servers :4, Number of regions : 116, HeapMemory for Region Server : 2GB &lt;/P&gt;&lt;P&gt;Quotas set :&lt;/P&gt;&lt;P&gt;TABLE =&amp;gt; ns1:table1 TYPE =&amp;gt; THROTTLE, THROTTLE_TYPE =&amp;gt; REQUEST_SIZE, LIMIT =&amp;gt; 10G/sec, SCOPE =&amp;gt; MACHINE&lt;/P&gt;&lt;P&gt;TABLE =&amp;gt; ns2:table2 TYPE =&amp;gt; THROTTLE, THROTTLE_TYPE =&amp;gt; REQUEST_SIZE, LIMIT =&amp;gt; 10G/sec, SCOPE =&amp;gt; MACHINE&lt;/P&gt;&lt;P&gt;Region server stack trace (notice below that the error is about &lt;STRONG&gt;read size limit&lt;/STRONG&gt; exceeded, and later the size of scan is only&lt;STRONG&gt; 28&lt;/STRONG&gt; (&lt;STRONG&gt;bytes&lt;/STRONG&gt;?). Stack trace:-&lt;/P&gt;&lt;P&gt;2016-09-17 22:35:40,674 DEBUG [B.defaultRpcServer.handler=55,queue=1,port=58526] quotas.RegionServerQuotaManager: &lt;STRONG&gt;Throttling exception&lt;/STRONG&gt; for user=root table=ns1:table1 numWrites=0 numReads=0 &lt;STRONG&gt;numScans=1&lt;/STRONG&gt;: &lt;STRONG&gt;read size limit exceeded&lt;/STRONG&gt; - &lt;STRONG&gt;wait 0.00sec&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;2016-09-17 22:35:40,676 DEBUG [B.defaultRpcServer.handler=55,queue=1,port=58526] ipc.RpcServer: B.defaultRpcServer.handler=55,queue=1,port=58526: callId: 52 service: ClientService methodName: &lt;STRONG&gt;Scan size: 28&lt;/STRONG&gt; connection: 10.65.141.170:42806
org.apache.hadoop.hbase.quotas.&lt;STRONG&gt;ThrottlingException&lt;/STRONG&gt;: &lt;STRONG&gt;read size limit exceeded - wait 0.00sec
&lt;/STRONG&gt;&lt;STRONG&gt;&lt;/STRONG&gt;at org.apache.hadoop.hbase.quotas.ThrottlingException.throwThrottlingException(ThrottlingException.java:107) &lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2016 11:21:53 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Limit-ressource-allocate-to-HBase-query-based-on-user/m-p/139703#M19326</guid>
      <dc:creator>sumit_nigam</dc:creator>
      <dc:date>2016-09-22T11:21:53Z</dc:date>
    </item>
  </channel>
</rss>

