[
https://issues.apache.org/jira/browse/HBASE-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16256181#comment-16256181
]
Dave Latham commented on HBASE-19148:
-------------------------------------
Will just mention a few of the configs that we run with where I wonder if the
default should be reconsidered. Apologies if some of these have already been
changed.
- hbase.master.loadbalance.bytable=true - If running with tables with
different workloads or profiles, it can be surprising to find a single table
very unbalanced on the cluster. Seems like it might be less surprising to keep
each table independently balanced. A tricky one I think.
- hbase.regionserver.fileSplitTimeout=600000 - Painful when the largest region
splits are the ones that fail, and gets stuck in a cycle where they fail worse.
- 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.
Don't feel strongly about any of them, but curious to see what other folks are
thinking.
> Edit of default configuration
> -----------------------------
>
> Key: HBASE-19148
> URL: https://issues.apache.org/jira/browse/HBASE-19148
> Project: HBase
> Issue Type: Bug
> Components: defaults
> Reporter: stack
> Priority: Blocker
> Fix For: 2.0.0-beta-1
>
>
> Remove cruft and mythologies. Make descriptions more digestible. Change
> defaults given experience.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
