[
https://issues.apache.org/jira/browse/HBASE-19505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16290439#comment-16290439
]
stack commented on HBASE-19505:
-------------------------------
bq. How I would see this is hbase.balancer.tablesOnMaster is the 1st parameter
to be set. If this is false (by default also) there will be NO regions in HM.
Whatever be the value of the 2nd config.
That is correct. First config says whether regions on master. Second config
allows you limit which type.
bq. The config hbase.balancer.tablesOnMaster.systemTablesOnly comes to action
when the 1st is true. And then by default we should put ONLY system tables on
HM. So this should have a default value of true.
Nah. hbase.balancer.tablesOnMaster.systemTablesOnly is the exotic config. You
should have to go out of your way to set this. Small clusters will want Master
to be like any other RegionServer in cluster and carry its weight of regions.
Thanks for looking into this. I did a bunch of testing putting these configs in
place (and IIRC, the is a parameterized test to confirm their workings...).
Seemed fine at the time.
Unfortunately, regions on master or not needs checking in lots of different
places.
> Disable ByteBufferPool by default at HM
> ---------------------------------------
>
> Key: HBASE-19505
> URL: https://issues.apache.org/jira/browse/HBASE-19505
> Project: HBase
> Issue Type: Sub-task
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19505.patch
>
>
> The main usage of the pool is while accepting bigger sized requests ie.
> Mutation requests. HM do not have any regions by default. So we can make
> this pool OFF in HM side. Still add a config to turn this ON.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
