[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697029#comment-13697029
]
Jean-Daniel Cryans commented on HBASE-8450:
-------------------------------------------
Not a big fan of late 0.94 changes to defaults. Imagine a situation where the
user tweaked the memstore lower/upper limits to use that 20% of the heap we're
not assigning, so now it would be >80%, and then deploys 0.94.10 via rolling
restart and the RS refuse to come back up because of that.
Basically the dynamics of the cluster would be different (maybe in a good way
or maybe not?).
To be fair, serious deploys would have those configurations tweaked so it
wouldn't change anything for them.
> 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
