[
https://issues.apache.org/jira/browse/HBASE-8450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662369#comment-13662369
]
Jean-Daniel Cryans commented on HBASE-8450:
-------------------------------------------
bq. From what I've seen, it's not that uncommon to have something above 60s,
and retrying just adds some workload on the server?
So originally I opened HBASE-4462 so that we stop retrying those timeouts, but
people agreed that HBASE-2937 (the operation timeout included in 0.92.0) was
covering that case. Passing an operation timeout actually changes the rpc
timeout at the same time, and it does cancel the retries in ServerCallable
(although in trunk I found out we don't change the rpc timeout, see HBASE-8581).
I agree with you that setting that down to 10 would currently mean that we
might retry timeouts on the region servers. What I'm wondering now is how we
can make this better. Should we also tweak the default operation timeout lower?
Maybe it set it higher for MR jobs?
> 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
>
>
> 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
