[
https://issues.apache.org/jira/browse/HBASE-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174884#comment-13174884
]
stack commented on HBASE-4956:
------------------------------
@Lars So supposition is that we bound the number of direct buffers client
allocates by bounding the number of threads in the thread pool (and have all
accesses go via the HTable thread pool)? If so, sounds good. What happens if
as many HTable instances as there are application-level threads and say the
application spawns lots of threads? The application should then go via
HTablePool? Or rather, you are suggesting that application uses new HBASE-4805
api and pass common executor to all HTable instances?
> 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
