[
https://issues.apache.org/jira/browse/HBASE-19148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295805#comment-16295805
]
stack commented on HBASE-19148:
-------------------------------
bq. That's the existing default in what we were running too, but we found 30
seconds was not enough for some large regions under load.
Oops. Thanks [~davelatham] Let me up it to what works on your cluster. I see
too that the config has changed in hbase2 now splits are run by master. Config
is now called hbase.master.fileSplitTimeout. Updated patch so it respects
hbase.regionserver.fileSplitTimeout if set.
Let me do your suggestion of doubling the block size and tuning way down the
0.95 threshold to 0.5 so we are more likely to avoid block transition yet we'll
be making WALs of about same size. Good one.
I put a mail up on the dev list to see if any objection to balance-by-table.
Will just implement unless objection.
Thanks for feeding us back your experience running in prod Dave.
> 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:
> 0002-HBASE-19148-Reevaluate-default-values-of-configurati.patch,
> 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)
