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/03/01 16:56:00 UTC

[jira] [Updated] (HBASE-20100) TestEnableTableProcedure flakey

     [ https://issues.apache.org/jira/browse/HBASE-20100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-20100:
--------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0-beta-2
           Status: Resolved  (was: Patch Available)

This is not on the flakies list. A  nightly did fail subsequent to this patch going in so we'll back here I think. Resolving this in the meantime.

> TestEnableTableProcedure flakey
> -------------------------------
>
>                 Key: HBASE-20100
>                 URL: https://issues.apache.org/jira/browse/HBASE-20100
>             Project: HBase
>          Issue Type: Sub-task
>          Components: amv2, flakey
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 2.0.0-beta-2
>
>         Attachments: HBASE-20100.branch-2.001.patch
>
>
> Failed in the nightly in interesting way. 
> https://builds.apache.org/job/HBase%20Nightly/job/branch-2/398/
> A subprocedure of enable table is assigning regions. The test is doing a kill of the procedure store  to ensure we can handle all state transtions even in face of failure. In this case, the kill of PE framework came in the finish of the assign procedure AFTER we'd updated hbase:meta and the internal AM state moving Region from OPENING to OPEN. Rerunning this step on restoration of the AMv2 WAL Store results in....
> {code}
> 2018-02-27 16:28:02,290 WARN  [PEWorker-1] assignment.RegionTransitionProcedure(331): Retryable error trying to transition: pid=64, ppid=52, state=RUNNABLE:REGION_TRANSITION_FINISH; AssignProcedure table=testRecoveryAndDoubleExecution, region=cdc8d2202f4aa4daf381bf1bf2e2fe0c; rit=OPEN, location=104080720bc8,38818,1519748808967
> org.apache.hadoop.hbase.exceptions.UnexpectedStateException: Expected [OFFLINE, CLOSED, SPLITTING, SPLIT, OPENING, FAILED_OPEN] so could move to OPEN but current state=OPEN
> {code}



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