[
https://issues.apache.org/jira/browse/HBASE-21573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731448#comment-16731448
]
stack commented on HBASE-21573:
-------------------------------
This should be cleaner now since hbase2... there is just operational timeout
(and scan IIRC). Let me add note in here w/ pointers to configs/doc. This issue
is about the Cosmin experience where current settings baffle when no cluster
up. [~psomogyi] You might have something to contrib here mighty Peter!
> 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: Critical
> Fix For: 2.1.3
>
>
> 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)
