You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/02/15 21:20:00 UTC

[jira] [Updated] (HBASE-19851) ProcV2 framework's rollback() needs to maintain stack like execute()

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

stack updated HBASE-19851:
--------------------------
    Priority: Critical  (was: Major)

> ProcV2 framework's rollback() needs to maintain stack like execute()
> --------------------------------------------------------------------
>
>                 Key: HBASE-19851
>                 URL: https://issues.apache.org/jira/browse/HBASE-19851
>             Project: HBase
>          Issue Type: Improvement
>          Components: proc-v2
>    Affects Versions: 2.0.0-beta-1
>            Reporter: Umesh Agashe
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> Refer to HBASE-19839 and detailed description there. Bug showed up as a flaky test TestMergeTableRegionsProcedure.testRollbackAndDoubleExecution(). In short, when rollback() is called after step 5 (MERGE_TABLE_REGIONS_CLOSE_REGIONS), rollback of the procedure tries to reassign two regions that are to be merged. It spawns 2 AssignProcedures and don't wait on them to finish. Rollback should have ability to have sub-procedures and separate proc stack.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)