[
https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848215#comment-17848215
]
Daniel Roudnitsky commented on HBASE-28608:
-------------------------------------------
In 2.x "meta operation timeout" really means "timeout to acquire the
userRegionLock needed to start a single region location lookup/meta scan".
> Client meta operation timeout does not default to the correct value
> -------------------------------------------------------------------
>
> Key: HBASE-28608
> URL: https://issues.apache.org/jira/browse/HBASE-28608
> Project: HBase
> Issue Type: Bug
> Components: Client
> Reporter: Daniel Roudnitsky
> Assignee: Daniel Roudnitsky
> Priority: Major
>
> Client meta operation timeout {{hbase.client.meta.operation.timeout}} default
> was intended to be set to the configured client operation timeout, but it
> defaults to the default client operation timeout of 20 minutes instead. This
> defeats the purpose of the meta operation timeout if one has
> {{hbase.client.operation.timeout}} < 20 minutes and does not explicitly set
> {{hbase.client.meta.operation.timeout}} . From "Timeout settings" in the
> hbase reference :
> {panel}
> A higher-level timeout is hbase.client.operation.timeout which is valid for
> each client call. When an RPC call fails for instance for a timeout due to
> hbase.rpc.timeout it will be retried until hbase.client.operation.timeout is
> reached. Client operation timeout for system tables can be fine tuned by
> setting hbase.client.meta.operation.timeout configuration value. When this is
> not set its value will use hbase.client.operation.timeout
> {panel}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
