[
https://issues.apache.org/jira/browse/HBASE-19505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16290414#comment-16290414
]
Anoop Sam John commented on HBASE-19505:
----------------------------------------
[~stack] How is the 2 configs working together? hbase.balancer.tablesOnMaster
which defaults to false and hbase.balancer.tablesOnMaster.systemTablesOnly also
defaults to false.
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.
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.
I started reading the usage of the configs in diff places.. Ya some places I
see this thinking is correct and code is been that way. Not sure all places.
The most concerning part is this
{code}
static boolean isSystemTablesOnlyOnMaster(Configuration conf) {
return conf.getBoolean(SYSTEM_TABLES_ON_MASTER, false);
}
{code}
where the system table alone is default marked false. So when one enables
tablesOnMaster to true, by default we will end up putting all regions.
If the basic idea on 2 configs is as what I say, pls confirm boss.. I started
checking the code and if any thing to be corrected, will open up jira.
> 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)
