Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 29 Jun 2017 16:36:00 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13083298.1498688088000.136057.1498754160062@Atlassian.JIRA>
In-Reply-To: <JIRA.13083298.1498688088000@Atlassian.JIRA>
References: <JIRA.13083298.1498688088000@Atlassian.JIRA> <JIRA.13083298.1498688088838@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HBASE-18290) Fix TestAddColumnFamilyProcedure and
 TestDeleteTableProcedure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 29 Jun 2017 16:36:04 -0000


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

stack updated HBASE-18290:
--------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

I pushed this. Will keep an eye on it. This patch might mess up my workaround but will deal with that separately.....

> 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
>             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
(v6.4.14#64029)