phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Soldatov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4459) Region assignments are failing for the test cases with extended clocks to support SCN
Date Tue, 02 Jan 2018 20:51:03 GMT

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

Sergey Soldatov commented on PHOENIX-4459:
------------------------------------------

The root cause is the new assignment manager which is relying on clock advancing when we perform
any transition ( i.e. we create a region with the current clock 1000, to open it clock should
be at least 1001, otherwise getTableState would not find it because it uses Get with exclusive
current timestamp). Since we are not advancing clock during currentTime() calls, it fails.
Not sure whether we may consider it's as a HBase bug, but a simple workaround is to make our
clock advancing every next call  currentTime

> Region assignments are failing for the test cases with extended clocks to support SCN
> -------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4459
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4459
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Rajeshbabu Chintaguntla
>            Assignee: Rajeshbabu Chintaguntla
>              Labels: HBase-2.0
>             Fix For: 5.0.0
>
>         Attachments: jstack_PHOENIX-4459
>
>
> There are test cases using own clock are failing with TableNotFoundException during region
assignment. The reason is the meta scan is not giving any results because of the past timestamps.
Need to check in more details. Because of the region assignment failures during create table
procedure hbase client wait for 30 mins. So not able to continue running the other tests as
well.
> {noformat}
> 2017-12-14 16:48:03,153 ERROR [ProcExecWrkr-9] org.apache.hadoop.hbase.master.TableStateManager(135):
Unable to get table T000008 state
> org.apache.hadoop.hbase.TableNotFoundException: T000008
> 	at org.apache.hadoop.hbase.master.TableStateManager.getTableState(TableStateManager.java:175)
> 	at org.apache.hadoop.hbase.master.TableStateManager.isTableState(TableStateManager.java:132)
> 	at org.apache.hadoop.hbase.master.assignment.AssignProcedure.startTransition(AssignProcedure.java:161)
> 	at org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:294)
> 	at org.apache.hadoop.hbase.master.assignment.RegionTransitionProcedure.execute(RegionTransitionProcedure.java:85)
> 	at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:845)
> 	at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1452)
> 	at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:1221)
> 	at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$800(ProcedureExecutor.java:77)
> 	at org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1731)
> {noformat}



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

Mime
View raw message