[
https://issues.apache.org/jira/browse/HBASE-21573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733232#comment-16733232
]
stack commented on HBASE-21573:
-------------------------------
This patch is really good. The doc is nice and clean. +1 . Should it be in a
subissue since this thing is about changing defaults (somehow).
Out of interest, do we have unit tests to ensure what we claim in the doc here?
I can check.....
Also, would be cool if on timeout, the message pointed to this nice section in
the refguide..... I could go through and do this too...
> More sensible client default timeout values
> -------------------------------------------
>
> Key: HBASE-21573
> URL: https://issues.apache.org/jira/browse/HBASE-21573
> Project: HBase
> Issue Type: Wish
> Components: Client
> Affects Versions: 2.1.1
> Reporter: Cosmin Lehene
> Assignee: Peter Somogyi
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: HBASE-21573.master.001.patch
>
>
> I guess the goal is to have operations allow enough time to recover from
> major failures.
> While this may make sense for large jobs, it's a PITA for OLTP scenarios and
> could probably benefit from a faster failure mode in default
>
> hbase.rpc.timeout = 60000
> hbase.client.operation.timeout = 1200000
> hbase.client.meta.operation.timeout = 1200000
> The client meta ops timeout is not in defaults-xml and not documented in the
> book either.
> [https://hbase.apache.org/book.html#config_timeouts]
>
> Would it make sense to have aggressive defaults instead?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
