[jira] [Updated] (HBASE-8234) Introducing "recovering" region state in AM to mark a region in recovering status used in distributedLogReplay

["stack (JIRA)" <ji...@apache.org>]

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

stack updated HBASE-8234:
-------------------------

    Fix Version/s:     (was: 0.95.2)

Moving out.  This improvement is not being worked on for 0.95/0.96 (though nice to have)
                
> Introducing "recovering" region state in AM to mark a region in recovering status used in distributedLogReplay
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-8234
>                 URL: https://issues.apache.org/jira/browse/HBASE-8234
>             Project: HBase
>          Issue Type: Sub-task
>          Components: MTTR
>            Reporter: Jeffrey Zhong
>
> There are two advantages to have this new "recovering" state in Assignment Manager for a region:
> 1) Instead of mark a region "recovering" in ZK, we can consolidate all region states in one place and be aware by assignment manager
> 2) When handing disabling table, we have to have this new state so that regions of a disabling table can be transitioned into this state for recovering.
> Notes:
> In the initial release of distributed log replay, we may not do this subtask for simplifications. Without the new state, we still need to create recovered edits files for regions of a disabling table. With the new state, we can retire recover edits files creation business totally.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira