You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Bob Copeland (JIRA)" <ji...@apache.org> on 2012/05/04 17:20:48 UTC

[jira] [Updated] (HBASE-4956) Control direct memory buffer consumption by HBaseClient

     [ https://issues.apache.org/jira/browse/HBASE-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bob Copeland updated HBASE-4956:
--------------------------------

    Attachment: thread_get.rb

Test script for reproducing the error (with max direct memory limits in place) or benchmarking different chunk sizes.  Although it can do threading, I have mostly passed "1" to do the tests in a single thread.
                
> 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
>         Attachments: thread_get.rb
>
>
> 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