hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1604) admins should be able to finalize namenode upgrades without running the cluster
Date Tue, 16 Oct 2007 05:10:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535058

Hadoop QA commented on HADOOP-1604:

-1 overall.  Here are the results of testing the latest attachment 
against trunk revision r584939.

    @author +1.  The patch does not contain any @author tags.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new compiler warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests -1.  The patch failed contrib unit tests.

Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/952/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/952/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/952/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/952/console

This message is automatically generated.

> admins should be able to finalize namenode upgrades without running the cluster
> -------------------------------------------------------------------------------
>                 Key: HADOOP-1604
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1604
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: dfs
>    Affects Versions: 0.14.0
>            Reporter: Owen O'Malley
>            Assignee: Konstantin Shvachko
>            Priority: Critical
>             Fix For: 0.15.0
>         Attachments: finalize.patch, finalize1.patch
> Currently a HDFS cluster must be running in order to finalize an upgrade, but if you
shut down without finalizing the new software won't start up. I propose a command line option
to the namenode that lets you finalize an upgrade with the cluster down.
> {code}
> % bin/hadoop namenode -finalize
> {code}

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message