You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Cosmin Lehene (JIRA)" <ji...@apache.org> on 2018/12/10 21:15:00 UTC
[jira] [Updated] (HBASE-21573) More sensible client default timeout
values
[ https://issues.apache.org/jira/browse/HBASE-21573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cosmin Lehene updated HBASE-21573:
----------------------------------
Issue Type: Wish (was: Bug)
> 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
> Priority: Major
> Fix For: 2.1.2
>
>
> 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)