You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/05/12 00:01:48 UTC
[jira] [Created] (HDFS-1919) Upgrade to federated namespace fails
Upgrade to federated namespace fails
------------------------------------
Key: HDFS-1919
URL: https://issues.apache.org/jira/browse/HDFS-1919
Project: Hadoop HDFS
Issue Type: Bug
Components: name-node
Affects Versions: 0.23.0
Reporter: Todd Lipcon
Priority: Blocker
Fix For: 0.23.0
I formatted a namenode running off 0.22 branch, and trying to start it on trunk yields:
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has clusterID mising.
It looks like 0.22 has LAYOUT_VERSION -33, but trunk has LAST_PRE_FEDERATION_LAYOUT_VERSION = -30, which is incorrect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1919) Upgrade to federated namespace fails
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032113#comment-13032113 ]
Todd Lipcon commented on HDFS-1919:
-----------------------------------
I patched too soon... this allows the upgrade and initial startup. But, then, on next start, the NN fails with:
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has no block pool Id.
> Upgrade to federated namespace fails
> ------------------------------------
>
> Key: HDFS-1919
> URL: https://issues.apache.org/jira/browse/HDFS-1919
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: hdfs-1919.txt
>
>
> I formatted a namenode running off 0.22 branch, and trying to start it on trunk yields:
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has clusterID mising.
> It looks like 0.22 has LAYOUT_VERSION -33, but trunk has LAST_PRE_FEDERATION_LAYOUT_VERSION = -30, which is incorrect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1919) Upgrade to federated namespace fails
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HDFS-1919:
------------------------------
Status: Patch Available (was: Open)
> Upgrade to federated namespace fails
> ------------------------------------
>
> Key: HDFS-1919
> URL: https://issues.apache.org/jira/browse/HDFS-1919
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: hdfs-1919.txt
>
>
> I formatted a namenode running off 0.22 branch, and trying to start it on trunk yields:
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has clusterID mising.
> It looks like 0.22 has LAYOUT_VERSION -33, but trunk has LAST_PRE_FEDERATION_LAYOUT_VERSION = -30, which is incorrect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1919) Upgrade to federated namespace fails
Posted by "Suresh Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032253#comment-13032253 ]
Suresh Srinivas commented on HDFS-1919:
---------------------------------------
There are plenty of upgrade related tests already in unit tests that cover lot of upgrade related tests and they do pass. Manual tests are done for upgrade from 203. Will do some tests related to upgrade from 0.22 - currently 0.22 is not a released software and I have not focused on testing that upgrade.
I can take over this bug.
> Upgrade to federated namespace fails
> ------------------------------------
>
> Key: HDFS-1919
> URL: https://issues.apache.org/jira/browse/HDFS-1919
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: hdfs-1919.txt
>
>
> I formatted a namenode running off 0.22 branch, and trying to start it on trunk yields:
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has clusterID mising.
> It looks like 0.22 has LAYOUT_VERSION -33, but trunk has LAST_PRE_FEDERATION_LAYOUT_VERSION = -30, which is incorrect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1919) Upgrade to federated namespace fails
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HDFS-1919:
------------------------------
Resolution: Duplicate
Status: Resolved (was: Patch Available)
Cannot reproduce after HDFS-1936 fixed layout version issues.
> Upgrade to federated namespace fails
> ------------------------------------
>
> Key: HDFS-1919
> URL: https://issues.apache.org/jira/browse/HDFS-1919
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Suresh Srinivas
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: hdfs-1919.txt
>
>
> I formatted a namenode running off 0.22 branch, and trying to start it on trunk yields:
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has clusterID mising.
> It looks like 0.22 has LAYOUT_VERSION -33, but trunk has LAST_PRE_FEDERATION_LAYOUT_VERSION = -30, which is incorrect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1919) Upgrade to federated namespace fails
Posted by "Suresh Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032256#comment-13032256 ]
Suresh Srinivas commented on HDFS-1919:
---------------------------------------
Todd, can you attach the log for next restart of NN where you got an exception.
> Upgrade to federated namespace fails
> ------------------------------------
>
> Key: HDFS-1919
> URL: https://issues.apache.org/jira/browse/HDFS-1919
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: hdfs-1919.txt
>
>
> I formatted a namenode running off 0.22 branch, and trying to start it on trunk yields:
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has clusterID mising.
> It looks like 0.22 has LAYOUT_VERSION -33, but trunk has LAST_PRE_FEDERATION_LAYOUT_VERSION = -30, which is incorrect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HDFS-1919) Upgrade to federated namespace fails
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon reassigned HDFS-1919:
---------------------------------
Assignee: Todd Lipcon
> Upgrade to federated namespace fails
> ------------------------------------
>
> Key: HDFS-1919
> URL: https://issues.apache.org/jira/browse/HDFS-1919
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: hdfs-1919.txt
>
>
> I formatted a namenode running off 0.22 branch, and trying to start it on trunk yields:
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has clusterID mising.
> It looks like 0.22 has LAYOUT_VERSION -33, but trunk has LAST_PRE_FEDERATION_LAYOUT_VERSION = -30, which is incorrect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1919) Upgrade to federated namespace fails
Posted by "Suresh Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032270#comment-13032270 ]
Suresh Srinivas commented on HDFS-1919:
---------------------------------------
I do not see any restarts failing. Perhaps you did not clean build and the static LV was not updated in some classes.
However, I do see that bumping up the layout version for 203, 22 and trunk (from HDFS-1842 and HDFS-1824) has caused problems with some of the version checks for new fsimage scheme of loading and checksum of edits etc. I will change the title of this bug and fix them.
> Upgrade to federated namespace fails
> ------------------------------------
>
> Key: HDFS-1919
> URL: https://issues.apache.org/jira/browse/HDFS-1919
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Suresh Srinivas
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: hdfs-1919.txt
>
>
> I formatted a namenode running off 0.22 branch, and trying to start it on trunk yields:
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has clusterID mising.
> It looks like 0.22 has LAYOUT_VERSION -33, but trunk has LAST_PRE_FEDERATION_LAYOUT_VERSION = -30, which is incorrect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-1919) Upgrade to federated namespace fails
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HDFS-1919:
------------------------------
Attachment: hdfs-1919.txt
Patch to fix LAST_PRE_FEDERATION_LAYOUT_VERSION
> Upgrade to federated namespace fails
> ------------------------------------
>
> Key: HDFS-1919
> URL: https://issues.apache.org/jira/browse/HDFS-1919
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: hdfs-1919.txt
>
>
> I formatted a namenode running off 0.22 branch, and trying to start it on trunk yields:
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has clusterID mising.
> It looks like 0.22 has LAYOUT_VERSION -33, but trunk has LAST_PRE_FEDERATION_LAYOUT_VERSION = -30, which is incorrect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1919) Upgrade to federated namespace fails
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032170#comment-13032170 ]
Hadoop QA commented on HDFS-1919:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12478896/hdfs-1919.txt
against trunk revision 1102094.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed these core unit tests:
org.apache.hadoop.cli.TestHDFSCLI
org.apache.hadoop.hdfs.TestDFSShell
org.apache.hadoop.hdfs.TestDFSStorageStateRecovery
org.apache.hadoop.hdfs.TestFileConcurrentReader
org.apache.hadoop.tools.TestJMXGet
+1 contrib tests. The patch passed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results: https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/488//testReport/
Findbugs warnings: https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/488//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/488//console
This message is automatically generated.
> Upgrade to federated namespace fails
> ------------------------------------
>
> Key: HDFS-1919
> URL: https://issues.apache.org/jira/browse/HDFS-1919
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: hdfs-1919.txt
>
>
> I formatted a namenode running off 0.22 branch, and trying to start it on trunk yields:
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has clusterID mising.
> It looks like 0.22 has LAYOUT_VERSION -33, but trunk has LAST_PRE_FEDERATION_LAYOUT_VERSION = -30, which is incorrect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HDFS-1919) Upgrade to federated namespace fails
Posted by "Nigel Daley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032250#comment-13032250 ]
Nigel Daley commented on HDFS-1919:
-----------------------------------
Was this caused by the federation branch merge? What testing was done on that before merge?
> Upgrade to federated namespace fails
> ------------------------------------
>
> Key: HDFS-1919
> URL: https://issues.apache.org/jira/browse/HDFS-1919
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: hdfs-1919.txt
>
>
> I formatted a namenode running off 0.22 branch, and trying to start it on trunk yields:
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has clusterID mising.
> It looks like 0.22 has LAYOUT_VERSION -33, but trunk has LAST_PRE_FEDERATION_LAYOUT_VERSION = -30, which is incorrect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HDFS-1919) Upgrade to federated namespace fails
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon reassigned HDFS-1919:
---------------------------------
Assignee: Suresh Srinivas (was: Todd Lipcon)
Hi Suresh. I'm reassigning this to you.
Unfortunately I don't have the log handy anymore, but you can easily reproduce by formatting the NN with 0.22, then running hadoop namenode -upgrade with trunk. It will start OK, but if you ^C and start again, it will fail with missing blockpool ID.
> Upgrade to federated namespace fails
> ------------------------------------
>
> Key: HDFS-1919
> URL: https://issues.apache.org/jira/browse/HDFS-1919
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Suresh Srinivas
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: hdfs-1919.txt
>
>
> I formatted a namenode running off 0.22 branch, and trying to start it on trunk yields:
> org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /tmp/name1 is in an inconsistent state: file VERSION has clusterID mising.
> It looks like 0.22 has LAYOUT_VERSION -33, but trunk has LAST_PRE_FEDERATION_LAYOUT_VERSION = -30, which is incorrect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira