[jira] [Commented] (HBASE-18290) Fix TestAddColumnFamilyProcedure and TestDeleteTableProcedure

["stack (JIRA)" <ji...@apache.org>]

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

stack commented on HBASE-18290:
-------------------------------

Pushed with a wonky JIRA ID

commit a022d09d53b4ef689dabad0f13d070373eecdca7
Author: Michael Stack <st...@apache.org>
Date:   Wed Jun 28 15:23:00 2017 -0700

    HBASE-HBASE-18290 Fix TestAddColumnFamilyProcedure and TestDeleteTableProcedure

> Fix TestAddColumnFamilyProcedure and TestDeleteTableProcedure
> -------------------------------------------------------------
>
>                 Key: HBASE-18290
>                 URL: https://issues.apache.org/jira/browse/HBASE-18290
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.0.0
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 2.0.0
>
>         Attachments: HBASE-18290.master.001.patch
>
>
> These two tests don't pass. Turns out the cause was interesting.
> We added a workaround for case where procedure WAL could have procs out of order.
> HBASE-18216 [AMv2] Workaround for HBASE-18152, corrupt procedure WAL
> If we find a procedure that is not 'increasing' -- of a later timestamp or procid -- then we'd skip the application of the 'old' proc. The workaround was until we figure in what scenarios we can write procedures out of order (seems to be rare and high-concurrency... TBD).
> These two tests trip FAILs and ROLLBACKs (double delete of table or disable of an already disabled table). They are good tests. But procedures that get marked FAIL or ROLLEDBACK will have procids that are less than current. Makes it so we skipped adding the ROLLBACK and so finishing up the procedure.



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