hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4956) Control direct memory buffer consumption by HBaseClient
Date Wed, 21 Dec 2011 07:05:31 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173917#comment-13173917

Lars Hofhansl commented on HBASE-4956:

Just checked the HTable code in trunk... Puts (even single put operations) already go through
a thread from the HTable's thread pool. A single get request is issuing a request directly,
but get(List<Get>) is also using the pool.
So limiting the number of threads in a single thread pool and using the new HTable constructor
from HBASE-4805, this can be controlled. Need to make one is using only get(List<Get>)
in addition to a relatively small global threadpool.
At Salesforce we'll shoot for pool with ~100 threads and a waiting queue of about 100 as well
(for very large clusters that may be too small though).

> Control direct memory buffer consumption by HBaseClient
> -------------------------------------------------------
>                 Key: HBASE-4956
>                 URL: https://issues.apache.org/jira/browse/HBASE-4956
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Ted Yu
> As Jonathan explained here https://groups.google.com/group/asynchbase/browse_thread/thread/c45bc7ba788b2357?pli=1
, standard hbase client inadvertently consumes large amount of direct memory.
> We should consider using netty for NIO-related tasks.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message