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

Hudson commented on HBASE-21437:
--------------------------------

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

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/596//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/master/596//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/master/596//JDK8_Nightly_Build_Report_(Hadoop3)/]


(x) {color:red}-1 source release artifact{color}
-- See build output for details.


(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console 
output|https://builds.apache.org/job/HBase%20Nightly/job/master/596//console].


> Bypassed procedure throw IllegalArgumentException when its state is 
> WAITING_TIMEOUT
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-21437
>                 URL: https://issues.apache.org/jira/browse/HBASE-21437
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.1.1, 2.0.2
>            Reporter: Jingyun Tian
>            Assignee: Jingyun Tian
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0, 2.0.3, 2.1.2
>
>         Attachments: HBASE-21437.master.001.patch, 
> HBASE-21437.master.002.patch, HBASE-21437.master.003.patch
>
>
> {code}
> 2018-11-05,18:25:52,735 WARN 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor: Worker terminating 
> UNNATURALLY null
> java.lang.IllegalArgumentException: NOT RUNNABLE! pid=3, 
> state=WAITING_TIMEOUT:REGION_STATE_TRANSITION_CLOSE, hasLock=true, 
> bypass=true; TransitRegionStateProcedure table=test_fail
> over, region=1bb029ba4ec03b92061be5c4329d2096, UNASSIGN
>         at 
> org.apache.hbase.thirdparty.com.google.common.base.Preconditions.checkArgument(Preconditions.java:134)
>         at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1620)
>         at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1384)
>         at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$1100(ProcedureExecutor.java:78)
>         at 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1948)
> 2018-11-05,18:25:52,736 TRACE 
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor: Worker terminated.
> {code}
> Since when we bypassed a WAITING_TIMEOUT procedure and resubmit it, its state 
> is still WAITING_TIMEOUT, then when executor run this procedure, it will 
> throw exception and cause worker terminated.



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

Reply via email to