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 Sat, 10 Mar 2018 04:16:00 GMT

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

Hudson commented on HBASE-20024:

Results for branch branch-2
	[build #466 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/466/]:
(x) *{color:red}-1 overall{color}*
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/466//General_Nightly_Build_Report/]

(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/466//JDK8_Nightly_Build_Report_(Hadoop2)/]

(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/466//JDK8_Nightly_Build_Report_(Hadoop3)/]

(/) {color:green}+1 source release artifact{color}
-- See build output for details.

> TestMergeTableRegionsProcedure is STILL flakey
> ----------------------------------------------
>                 Key: HBASE-20024
>                 URL: https://issues.apache.org/jira/browse/HBASE-20024
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Umesh Agashe
>            Priority: Major
>             Fix For: 2.0.0
>         Attachments: HBASE-20024.branch-2.001.patch, hbase-20024.master.001.patch, hbase-20024.master.002.patch,
hbase-20024.master.003.patch, hbase-20024.master.004.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