[
https://issues.apache.org/jira/browse/HBASE-28608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Roudnitsky updated HBASE-28608:
--------------------------------------
Description:
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 a typical setup
where {{hbase.client.operation.timeout}} << 20 minutes and
{{hbase.client.meta.operation.timeout}} is not explicitly set, which can lead
to operations taking much longer than the configured operation timeout to
actually timeout if there is e.g meta slowness and/or contention around
userRegionLock on 2.x. 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}
was:
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 a typical setup
where {{hbase.client.operation.timeout}} << 20 minutes and
{{hbase.client.meta.operation.timeout}} is not explicitly set, which can lead
to operations taking much longer than the operation timeout to timeout if there
is meta slowness or contention around u . 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}
> 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
> Affects Versions: 2.6.0, 2.4.17, 3.0.0-beta-1, 2.5.8
> Reporter: Daniel Roudnitsky
> Assignee: Daniel Roudnitsky
> Priority: Major
> Labels: timeout
>
> 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 a typical setup
> where {{hbase.client.operation.timeout}} << 20 minutes and
> {{hbase.client.meta.operation.timeout}} is not explicitly set, which can lead
> to operations taking much longer than the configured operation timeout to
> actually timeout if there is e.g meta slowness and/or contention around
> userRegionLock on 2.x. 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)
