You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/04/06 21:32:00 UTC
[jira] [Resolved] (HBASE-20203) [AMv2] CODE-BUG: Uncaught runtime
exception for pid=...., state=SUCCESS; AssignProcedure
[ https://issues.apache.org/jira/browse/HBASE-20203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-20203.
---------------------------
Resolution: Cannot Reproduce
Resovling as 'cannot reproduce'. Have not seen it in a good while. Will open new issue if I run into it.
> [AMv2] CODE-BUG: Uncaught runtime exception for pid=...., state=SUCCESS; AssignProcedure
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-20203
> URL: https://issues.apache.org/jira/browse/HBASE-20203
> Project: HBase
> Issue Type: Bug
> Components: amv2
> Affects Versions: 2.0.0-beta-2
> Reporter: stack
> Assignee: stack
> Priority: Critical
> Fix For: 2.0.0
>
>
> This is an odd one. Causes ITBLL to fail because region is offline.
> Two seconds after reporting Finished, successful assign, another thread tries to finish the Procedure. The second run messes us up.
> {code}
> 2018-03-14 11:04:07,987 INFO [PEWorker-1] procedure2.ProcedureExecutor: Finished pid=3600, ppid=3591, state=SUCCESS; AssignProcedure table=IntegrationTestBigLinkedList, region=b58e6e7c3b2e449f80533ea999707319 in 4.4100sec
> ....
> 2018-03-14 11:04:10,600 INFO [PEWorker-2] procedure.MasterProcedureScheduler: pid=3600, ppid=3591, state=SUCCESS; AssignProcedure table=IntegrationTestBigLinkedList, region=b58e6e7c3b2e449f80533ea999707319, IntegrationTestBigLinkedList,\x9Ey\xE7\x9Ey\xE7\x9Ep,1521050540660.b58e6e7c3b2e449f80533ea999707319.
> 2018-03-14 11:04:10,606 ERROR [PEWorker-2] procedure2.ProcedureExecutor: CODE-BUG: Uncaught runtime exception for pid=3600, ppid=3591, state=SUCCESS; AssignProcedure table=IntegrationTestBigLinkedList, region=b58e6e7c3b2e449f80533ea999707319 java.lang.UnsupportedOperationException: Unhandled state REGION_TRANSITION_FINISH; there is no rollback for assignment unless we cancel the operation by dropping/disabling the table
> at org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.rollback(RegionTransitionProcedure.java:345) at org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.rollback(RegionTransitionProcedure.java:86) at org.apache.hadoop.hbase.procedure2.Procedure.doRollback(Procedure.java:859)
> at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeRollback(ProcedureExecutor.java:1353)
> at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeRollback(ProcedureExecutor.java:1309) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1178)
> at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$800(ProcedureExecutor.java:75) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1740)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)