You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2007/07/12 22:10:04 UTC
[jira] Created: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
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: Bug
Components: dfs
Affects Versions: 0.14.0
Reporter: Owen O'Malley
Assignee: Konstantin Shvachko
Priority: Blocker
Fix For: 0.14.0
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.
[jira] Updated: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko updated HADOOP-1604:
----------------------------------------
Status: Patch Available (was: Open)
> 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.
[jira] Updated: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-1604:
-------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks Konstantin!
> 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.16.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.
[jira] Updated: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sameer Paranjpye updated HADOOP-1604:
-------------------------------------
Fix Version/s: (was: 0.14.0)
0.15.0
> 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
>
>
> 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.
[jira] Updated: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated HADOOP-1604:
---------------------------------
Not a regression, moving to 0.16 release.
> 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.16.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.
[jira] Commented: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534990 ]
Raghu Angadi commented on HADOOP-1604:
--------------------------------------
+1.
One cosmetic change : on DFS front page, this adds a new row to {{dfstable}}, since this row has two lines sometimes, could you make the the table cell's vertical alignment to 'top' in hadoop.css?
> 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
>
>
> 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.
[jira] Updated: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghu Angadi updated HADOOP-1604:
---------------------------------
Priority: Critical (was: Blocker)
> 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.14.0
>
>
> 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.
[jira] Updated: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko updated HADOOP-1604:
----------------------------------------
Attachment: finalize.patch
This patch introduces -finalize option for starting the name-node.
When started with -finalize name-node removes previous directories if any and exits.
There is no need to start data-node at this time.
After that the cluster can be started regularly, and the data-nodes will perform finalize on there own.
Reporting is also improved as requested. Non finalized upgrade is reported by
# dfsadmin -report
# dfsadmin -upgradeProgress
# and web UI prints the upgrade status
> 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
>
>
> 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.
[jira] Commented: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536196 ]
Hudson commented on HADOOP-1604:
--------------------------------
Integrated in Hadoop-Nightly #277 (See [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/277/])
> 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.16.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.
[jira] Updated: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko updated HADOOP-1604:
----------------------------------------
Issue Type: New Feature (was: Bug)
I agree it would be useful to have -finalize option for the name-node startup.
This is a new feature. Not a bug. Do we have feature freeze in progress for 0.14 already?
> 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: Blocker
> Fix For: 0.14.0
>
>
> 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.
[jira] Commented: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
Posted by "Enis Soztutar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514576 ]
Enis Soztutar commented on HADOOP-1604:
---------------------------------------
A funny mistake, but once we have somehow "forgotten" to finalize the upgrade from 0.9 to 0.13. We haven't realized this until DFS grew to use all the disk space (because of the previous directories) . So it would be really informative, if the UI and the command line logs show that the dfs is in the status of upgrading, and it should the finalized, similar to the safety-mode messages.
> 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.14.0
>
>
> 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.
[jira] Updated: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley updated HADOOP-1604:
----------------------------------
Fix Version/s: (was: 0.15.0)
0.16.0
> 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.16.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.
[jira] Commented: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ 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
http://issues.apache.org/jira/secure/attachment/12367794/finalize1.patch
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.
[jira] Updated: (HADOOP-1604) admins should be able to finalize
namenode upgrades without running the cluster
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko updated HADOOP-1604:
----------------------------------------
Attachment: finalize1.patch
Made changes to hadoop.css
# removed 40% width constraint for the dfstable
# set vertical alignment to top
# html page retains line breaks, before that it was ignoring them.
> 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.