You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Rushabh Shah (Jira)" <ji...@apache.org> on 2020/09/05 18:36:00 UTC

[jira] [Created] (HBASE-24983) Wrap ConnectionImplemetation#locateRegioninMeta under operation timeout.

Rushabh Shah created HBASE-24983:
------------------------------------

             Summary: Wrap ConnectionImplemetation#locateRegioninMeta under operation timeout.
                 Key: HBASE-24983
                 URL: https://issues.apache.org/jira/browse/HBASE-24983
             Project: HBase
          Issue Type: Bug
          Components: Client
    Affects Versions: 1.6.0
            Reporter: Rushabh Shah


We have config property (hbase.client.operation.timeout and hbase.client.meta.operation.timeout).
Description of hbase.client.operation.timeout which is for non meta tables.
{noformat}
Operation timeout is a top-level restriction (millisecond) that makes sure a blocking operation in Table will not be blocked more than this. In each operation, if rpc request fails because of timeout or other reason, it will retry until success or throw RetriesExhaustedException. But if the total time being blocking reach the operation timeout before retries exhausted, it will break early and throw SocketTimeoutException.
{noformat}

Most of the operations like get, put, delete are wrapped under this timeout but scan operation is not wrapped in this timeout. We need to wrap scan operations also within operation timeout.
More discussion in this PR thread:  https://github.com/apache/hbase/pull/2322#discussion_r478687341



--
This message was sent by Atlassian Jira
(v8.3.4#803005)