[jira] [Comment Edited] (HBASE-21573) More sensible client default timeout values

["Lars Hofhansl (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-21573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730948#comment-16730948 ] 

Lars Hofhansl edited comment on HBASE-21573 at 12/30/18 11:20 AM:
------------------------------------------------------------------

I have long thought that all these config options are a PITA :)
hbase.rpc.timeout
hbase.rpc.read.timeout
hbase.rpc.write.timeout
hbase.client.operation.timeout
hbase.client.scanner.timeout
hbase.client.meta.operation.timeout
etc

Do we really need so many different options?
Perhaps there can be one or two profiles. Or at least some of the these can be set depending on the others...


was (Author: lhofhansl):
I have long thought that all these config options are a PITA :)


> 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.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)