hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-20024) TestMergeTableRegionsProcedure is STILL flakey
Date Wed, 21 Feb 2018 03:06:00 GMT

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

Hudson commented on HBASE-20024:

SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #4620 (See [https://builds.apache.org/job/HBase-Trunk_matrix/4620/])
HBASE-20024 TestMergeTableRegionsProcedure is STILL flakey (stack: rev 51cea3e2c3c75b82148f14ca7903a88daa3738d9)
* (edit) hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/StateMachineProcedure.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/SplitTableRegionProcedure.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/MergeTableRegionsProcedure.java
* (edit) hbase-procedure/src/main/java/org/apache/hadoop/hbase/procedure2/ProcedureExecutor.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/DeleteTableProcedure.java
* (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/master/assignment/TestMergeTableRegionsProcedure.java
* (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/master/procedure/MasterProcedureTestingUtility.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/master/procedure/MasterProcedureScheduler.java

> TestMergeTableRegionsProcedure is STILL flakey
> ----------------------------------------------
>                 Key: HBASE-20024
>                 URL: https://issues.apache.org/jira/browse/HBASE-20024
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>         Attachments: HBASE-20024.branch-2.001.patch
> This is a follow-on from HBASE-20015. Root issue is that merge does not support rollback
once it has hit the point-of-no-return; it can only roll-forward at this point.
> HBASE-18018 added abort to all procedures. HBASE-18016 added ignoring abort to the truncate
procedure to get around flakeyness. HBASE-20022 is a new issue to figure what to do w/ unabortable
> Meantime, merge and split have PONR and the procedure executor test harness does abort
regardless making these tests flakies. Adding an ignore of the abort once into the PONR makes
sense (Always? HBASE-20022 is for those as yet unknown cases where it does not). Let me ignore
to merge and split in this issue to address flakeyness.

This message was sent by Atlassian JIRA

View raw message