[
https://issues.apache.org/jira/browse/HBASE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370979#comment-16370979
]
stack commented on HBASE-20024:
-------------------------------
We are on to a new failure type.
java.lang.AssertionError: expected:<true> but was:<false>
at
org.apache.hadoop.hbase.master.assignment.TestMergeTableRegionsProcedure.testRollbackAndDoubleExecution(TestMergeTableRegionsProcedure.java:273)
Happens in the PONR test too but only on GCE it seems... so it not disturbing
nightlies.
Our incidence does not seem to have gone down though. It has just changed.
[~uagashe] Want to have a look at this one?
> 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 procedures.
> 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
(v7.6.3#76005)
