Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.1.1, 2.0.2
-
None
-
None
Description
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.
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.
Attachments
Attachments
Issue Links
- links to