hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Heng Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16664) Timeout logic in AsyncProcess is broken
Date Wed, 12 Oct 2016 03:02:21 GMT

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

Heng Chen commented on HBASE-16664:

Normally we share one HTable object in our application.   It is hard to avoid race condition.
I think we should define the operation timeout firstly to avoid conflicts. 
This is our description for it in hbase-default.xml
    <description>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
      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
      before retries exhausted, it will break early and throw SocketTimeoutException.</description>

what's the one operation?  Batch is one operation?  [~stack]

> Timeout logic in AsyncProcess is broken
> ---------------------------------------
>                 Key: HBASE-16664
>                 URL: https://issues.apache.org/jira/browse/HBASE-16664
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>         Attachments: 1.patch, HBASE-16664-branch-1-v1.patch, HBASE-16664-branch-1-v1.patch,
HBASE-16664-branch-1.1-v1.patch, HBASE-16664-branch-1.2-v1.patch, HBASE-16664-branch-1.3-v1.patch,
HBASE-16664-v1.patch, HBASE-16664-v2.patch, HBASE-16664-v3.patch, HBASE-16664-v4.patch, HBASE-16664-v5.patch,
> Have not checked the root cause, but I think timeout of all operations in AsyncProcess
is broken

This message was sent by Atlassian JIRA

View raw message