[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653106#comment-13653106
]
Nick Dimiduk commented on HBASE-8450:
-------------------------------------
{quote}
- hfile.block.cache.size=0.4: Since we let users dedicate up to 80% of the heap
for the block cache and Memstores, we should fully use that space by default.
I've stopped counting the numbers I've told people that they had all this
memory that's not being used because they were keeping the configs default...
Right now we're at 25/40 so I'd just bump up the block cache to 40. Even better
would be doing HBASE-5349...
- hbase.regionserver.handler.count=50: or it could be 100, I don't really have
data on this.
- hbase.client.pause=100: make everything snappier? might want to bump up the
number of retries. I don't have data on this.
hbase.rpc.timeout=10000: snappier I said!
{quote}
+1 for the above.
- hbase.client.write.buffer at 2M plus hbase.regionserver.handler.count at 10
sounds conservative to me, even considering JD's block cache size tweak.
- hbase.bulkload.retries.number I recall seeing a ticket where the unlimited
retries was causing havoc, but I cannot find it this morning.
- hbase.client.scanner.caching this number is entirely arbitrary, given
variance in data shape. Do we still like 100?
- hbase.hregion.memstore.flush.size is the same value as default hdfs block
size. dumb question: should this be slightly less than the hdfs block size in
order to accommodate headers and trailers?
- hbase.config.read.zookeeper.config can this configuration point be removed
entirely? Is there ever a reason to read zoo.cfg?
Cleaning up the file with spell-check and sort by property name would be nice
too ;)
> 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
> Priority: Critical
> Fix For: 0.95.1
>
> Attachments: 8450.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
