You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Anoop Sam John (JIRA)" <ji...@apache.org> on 2016/11/11 07:29:58 UTC

[jira] [Commented] (HBASE-17073) Increase the max number of buffers in ByteBufferPool

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

Anoop Sam John commented on HBASE-17073:
----------------------------------------

[~saint.ack@gmail.com], [~ram_krish]  what do u say?

> Increase the max number of buffers in ByteBufferPool
> ----------------------------------------------------
>
>                 Key: HBASE-17073
>                 URL: https://issues.apache.org/jira/browse/HBASE-17073
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0
>
>
> Before the HBASE-15525 issue fix, we had variable sized buffers in our buffer pool. The max size upto which one buffer can grow was 2 MB.  Now we have changed it to be a fixed sized BBPool. By default 64 KB is the size of each buffer.  But the max number of BBs allowed to be in the pool was not changed.  ie. twice the number of handlers. May be we should be changing increasing it now?  To make it equal to the way like 2 MB, we will need 32 * 2 * handlers.  There is no initial #BBs any way. 2 MB is the default max response size what we have. And write reqs also, when it is Buffered mutator 2 MB is the default flush limit.  We can make it to be 32 * #handlers as the def max #BBs I believe.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)