You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/11 19:52:00 UTC

[jira] [Resolved] (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 ]

Andrew Kyle Purtell resolved HBASE-21573.
-----------------------------------------
      Assignee:     (was: Vladimir Rodionov)
    Resolution: Abandoned

> 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
>         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
(v8.20.7#820007)