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

Hudson commented on HBASE-21073:
--------------------------------

Results for branch branch-2.0
        [build #1002 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1002/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1002//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1002//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1002//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> "Maintenance mode" master
> -------------------------
>
>                 Key: HBASE-21073
>                 URL: https://issues.apache.org/jira/browse/HBASE-21073
>             Project: HBase
>          Issue Type: Sub-task
>          Components: amv2, hbck2, master
>            Reporter: stack
>            Assignee: Mike Drob
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0, 2.1.1, 2.0.3
>
>         Attachments: HBASE-21073.branch-2.001.patch, 
> HBASE-21073.branch-2.1.001.patch, HBASE-21073.branch-2.1.002.patch, 
> HBASE-21073.master.001.patch, HBASE-21073.master.002.patch, 
> HBASE-21073.master.003.patch, HBASE-21073.master.004.patch, 
> HBASE-21073.master.005.patch, HBASE-21073.master.006.patch, 
> HBASE-21073.master.007.patch, HBASE-21073.master.008.patch, 
> HBASE-21073.master.009.patch, HBASE-21073.master.010.patch, 
> HBASE-21073.master.011.patch
>
>
> Make it so we can bring up a Master in "maintenance mode". This is parse of 
> master wal procs but not taking on regionservers. It would be in a state 
> where "repair" Procedures could run; e.g. a Procedure that could recover meta 
> by looking for meta WALs, splitting them, dropping recovered.edits, and even 
> making it so meta is readable. See parent issue for why needed (disaster 
> recovery).



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

Reply via email to