[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662095#comment-13662095
]
stack commented on HBASE-8450:
------------------------------
[~lhofhansl] On delete marker never getting deleted, my thinking is that this
would not be the end of the world and second, frequently compactions are
promoted to major compaction because all files are selected so deletes would
get purged (The general call is that disabling major compactions will be
overall better than retention of deletes; do you disagree w/ this?). On the
suggestion that FAST_DIFF slows down scan, let me put up a new patch that does
not enable it; your comment puts it into that bucket of configs that we should
change only after we do some testing.
Let me make a new patch.
> 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
>
>
> 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
