[
https://issues.apache.org/jira/browse/HBASE-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16293552#comment-16293552
]
stack commented on HBASE-19148:
-------------------------------
[~davelatham] some questions sir
I think 'hbase.master.loadbalance.bytable=true' makes sense as default on big
cluster where tables are big, less so on small cluster (i think). Looking at
the stochastic balancer, it has this in the class comment:
* <p>This balancer is best used with hbase.master.loadbalance.bytable set to
false
* so that the balancer gets the full picture of all loads on the cluster.</p>
Let me add this config to hbase-default so folks see at least it is there.
hbase.regionserver.fileSplitTimeout=30000 in branch-2. This better?
bq. hbase.regionserver.logroll.multiplier=0.5 - With the default of 0.95,
whenever write load was significant, we saw many log files that had a little
bit more than 1 HDFS block worth of data. Seemed a waste.
So, we'd run over the block size because 0.95 doesn't give us enough wiggly
room within which to close the WAL? We could come down from 0.95. 0.5 seems way
down. We'd make lots of files -- a pain in itself. Set it at 0.8? Should we
up the default block size?
> Reevaluate default values of configurations
> -------------------------------------------
>
> Key: HBASE-19148
> URL: https://issues.apache.org/jira/browse/HBASE-19148
> Project: HBase
> Issue Type: Bug
> Components: defaults
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19148.master.001.patch
>
>
> Remove cruft and mythologies. Make descriptions more digestible. Change
> defaults given experience.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
