[ https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664473#comment-13664473 ]
stack commented on HBASE-8450: ------------------------------ Just to add that I had to fix a bunch of unit tests because they were expecting max values to be the default 3 and because a few tests were expecting one encoding type only in block cache (w/ blooms on, it has blocks in the cache w/ encoding NONE which was messing up some expectations) > Update hbase-default.xml and general recommendations to better suit current > hw, h2, experience, etc. > ---------------------------------------------------------------------------------------------------- > > 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