[
https://issues.apache.org/jira/browse/HADOOP-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587839#action_12587839
]
Hadoop QA commented on HADOOP-2585:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12379900/SecondaryStorage.patch
against trunk revision 645773.
@author +1. The patch does not contain any @author tags.
tests included +1. The patch appears to include 3 new or modified tests.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler
warnings.
release audit +1. The applied patch does not generate any new release
audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests -1. The patch failed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2202/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2202/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2202/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2202/console
This message is automatically generated.
> Automatic namespace recovery from the secondary image.
> ------------------------------------------------------
>
> Key: HADOOP-2585
> URL: https://issues.apache.org/jira/browse/HADOOP-2585
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Affects Versions: 0.16.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: 0.18.0
>
> Attachments: SecondaryStorage.patch, SecondaryStorage.patch
>
>
> Hadoop has a three way (configuration controlled) protection from loosing the
> namespace image.
> # image can be replicated on different hard-drives of the same node;
> # image can be replicated on a nfs mounted drive on an independent node;
> # a stale replica of the image is created during periodic checkpointing and
> stored on the secondary name-node.
> Currently during startup the name-node examines all configured storage
> directories, selects the
> most up to date image, reads it, merges with the corresponding edits, and
> writes to the new image back
> into all storage directories. Everything is done automatically.
> If due to multiple hardware failures none of those images on mounted hard
> drives (local or remote)
> are available the secondary image although stale (up to one hour old by
> default) can be still
> used in order to recover the majority of the file system data.
> Currently one can reconstruct a valid name-node image from the secondary one
> manually.
> It would be nice to support an automatic recovery.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
