hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18390) Sleep too long when finding region location failed
Date Wed, 19 Jul 2017 09:46:01 GMT

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

Phil Yang commented on HBASE-18390:
-----------------------------------

I reset to the previous commit af359d03b5e2cc798cee8ba52d2a9fcbb1022104  it is also failed.
So it is not broken by this issue.

> Sleep too long when finding region location failed
> --------------------------------------------------
>
>                 Key: HBASE-18390
>                 URL: https://issues.apache.org/jira/browse/HBASE-18390
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.3.1, 1.2.6, 1.1.11, 2.0.0-alpha-1
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>             Fix For: 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7, 2.0.0-alpha-2, 1.1.12
>
>         Attachments: HBASE-18390.v01.patch, HBASE-18390.v02.patch, HBASE-18390.v03.patch
>
>
> If RegionServerCallable#prepare failed when getRegionLocation, the location in this callable
object is null. And before we retry we will sleep. However, when location is null we will
sleep at least 10 seconds. And the request will be failed directly if operation timeout is
less than 10 seconds. I think it is no need to keep MIN_WAIT_DEAD_SERVER logic. Use backoff
sleeping logic is ok for most cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message