hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8234) Introducing "recovering" region state in AM to mark a region in recovering status used in distributedLogReplay
Date Tue, 01 Apr 2014 15:57:24 GMT

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

stack commented on HBASE-8234:
------------------------------

[~jeffreyz] Is this nice-to-have or a requirement when we have distributed log replay enabled?
 If table is disabling will we lose data w/o it?  Thanks [~jeffreyz]

> 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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message