hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-8450) Update hbase-default.xml and general recommendations to better suit current hw, h2, experience, etc.
Date Wed, 22 May 2013 21:28:21 GMT

     [ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-8450:

    Release Note: 
Changed defaults:

+ max versions now 1 instead of 3
+ row blooms on by default (except on .META. table)
+ handlers 30 instead of 10
+ upped memstore lower limit from .35 to .38
+ zookeeper timeout default is 90seconds instead of 180
+ client pause is 100ms instead of 1000ms
+ retries are now 20 instead of 10 (so overall we still wait same amount of time)
+ bulkload retries is 10 instead of infinite
+ major compactions are now once a week instead of once every 24 hours; they are staggered
so all regionservers do not start compacting at the same time
+ blockingstorefiles is 10 instead of 7
+ block cache is 0.4 instead of 0.25

Let me make sure that old tables post-migration do not all of a sudden start have max version
of 1.
> Update hbase-default.xml and general recommendations to better suit current hw, h2, experience,
> ----------------------------------------------------------------------------------------------------
>                 Key: HBASE-8450
>                 URL: https://issues.apache.org/jira/browse/HBASE-8450
>             Project: HBase
>          Issue Type: Task
>          Components: Usability
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 0.95.1
>         Attachments: 8450.txt, 8450v2.txt, 8450v3.txt, 8450v5.txt, 8450v5.txt
> This is a critical task we need to do before we release; review our defaults.
> On cursory review, there are configs in hbase-default.xml that no longer have matching
code; there are some that should be changed because we know better now and others that should
be amended because hardware and deploys are bigger than they used to be.
> We could also move stuff around so that the must-edit stuff is near the top (zk quorum
config. is mid-way down the page) and beef up the descriptions -- especially since these descriptions
shine through in the refguide.
> Lastly, I notice that our tgz does not "include" an hbase-default.xml other than the
one bundled up in the jar.  Maybe we should make it more accessible.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message