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

Umesh Agashe commented on HBASE-20024:
--------------------------------------

[~stack], as we discussed I have added more comments explicitly calling out 
current assumptions and modifications needed if and when in future assumptions 
may not be true. Please review the changes and let me know. Thanks!

> 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 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)

Reply via email to