[
https://issues.apache.org/jira/browse/HBASE-18662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16159976#comment-16159976
]
Chia-Ping Tsai commented on HBASE-18662:
----------------------------------------
bq. Another point I have is we cannot change the default value of
hbase.regionserver.region.split.policy in the java code it will change the
behaviour of region splitting if user has not configured this configuration and
assuming that default split policy is IncreasingToUpperBoundRegionSplitPolicy.
The hbase-default.xml is included in hbase-common.jar, so the
HBaseConfiguration.create() always *load* hbase-default.xml first before
hbase-site.xml. If user doesn't set any config of split policy, the policy
retrieved from configuration should be same with hbase-default.xml . Why does
user assume the default is IncreasingToUpperBoundRegionSplitPolicy?
Furthermore, our docs also says "the default split policy is
SteppingSplitPolicy".
> The default values for many configuration items in the code are not
> consistent with hbase-default.xml
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-18662
> URL: https://issues.apache.org/jira/browse/HBASE-18662
> Project: HBase
> Issue Type: Improvement
> Reporter: Yun Zhao
> Assignee: Yun Zhao
> Priority: Minor
> Fix For: 2.0.0-alpha-3
>
> Attachments: HBASE-18662.master.002.patch
>
>
> Such as
> {code}
> hbase.ipc.server.callqueue.handler.factor
> hbase.regionserver.logroll.errors.tolerated
> hbase.regionserver.region.split.policy
> zookeeper.session.timeout
> hbase.client.retries.number
> hbase.client.max.perserver.tasks
> hbase.client.keyvalue.maxsize
> hbase.normalizer.period
> hbase.hstore.blockingStoreFiles
> hbase.snapshot.restore.take.failsafe.snapshot
> hbase.lease.recovery.dfs.timeout
> hbase.rest.filter.classes
> hbase.http.max.threads
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
