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

Hudson commented on HBASE-22343:
--------------------------------

Results for branch branch-2
        [build #1866 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1866/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(x) {color:red}-1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1866//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1866//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1866//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Make procedure retry interval configurable in test
> --------------------------------------------------
>
>                 Key: HBASE-22343
>                 URL: https://issues.apache.org/jira/browse/HBASE-22343
>             Project: HBase
>          Issue Type: Bug
>          Components: amv2, test
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0, 2.3.0
>
>
> I think the problem is related to HBASE-22193, where we add exponential 
> backoff when failing to open a region. Saw this in the output
> {noformat}
> 2019-04-29 20:43:09,624 WARN  [PEWorker-24] 
> assignment.TransitRegionStateProcedure(351): Failed transition, suspend 
> 129secs pid=15, state=RUNNABLE:REGION_STATE_TRANSITION_GET_ASSIGN_CANDIDATE, 
> hasLock=true; 
> {noformat}
> And the wait time is 180 seconds, so we time out...
> Maybe we should introduce a max wait time config, and set it to a small value 
> in this test...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to