hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1242) dfs upgrade/downgrade problems
Date Fri, 11 May 2007 20:52:15 GMT

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

Owen O'Malley commented on HADOOP-1242:

>   1.  By design the storage file is an indicator that the old layout is present.
>     The order is important since the recovery is based on that order.

The "storage" file is a bad indicator precisely because the pre-13 versions of Hadoop's datanodes
create it without question. The "data" directory is a much much better indicator, because
it is _not_ created automatically. This is far too common a case to allow Hadoop's automatic
upgrade to corrupt you data node's directory.

> I think this works as designed.

It may work the way that you intended it, but it is really bad from a usability standpoint.
My change isn't perfect, but it handles it much better and you haven't provided any use cases
where it is worse.

> You made a mistake, the software detected inconsistency and warned you. 

Which is fine, except it also corrupted the repository such that I had to make hand edits
to each node in the cluster to fix the problem. That is not ok.

> I do not understand what is expected here. I do not understand what is it blocking.

What is expected is that if you try to bring up a version 12 data node on a version 13 data
node directory it will fail. However, when you fix the problem and use version 13 again, it
must come up without a problem. Making the administrator log into every single node to delete
a file is not ok.

> dfs upgrade/downgrade problems
> ------------------------------
>                 Key: HADOOP-1242
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1242
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.13.0
>            Reporter: Owen O'Malley
>         Assigned To: dhruba borthakur
>            Priority: Blocker
>             Fix For: 0.13.0
>         Attachments: clean-upgrade.patch
> I ran my test cluster on 0.13 and then tried to run it under 0.12. When I downgraded,
the namenode would not come up and the message said I needed to format the filesystem. I ignored
that and tried to restart on 0.13, now the datanode will not come up with:
> 2007-04-10 11:25:37,448 ERROR org.apache.hadoop.dfs.DataNode: org.apache.hadoop.
> dfs.InconsistentFSStateException: Directory /local/owen/hadoop/dfs/d
> ata is in an inconsistent state: Old layout block directory /local/owen/hadoop/dfs/data/data
is missing
>         at org.apache.hadoop.dfs.DataStorage.isConversionNeeded(DataStorage.java
> :170)
>         at org.apache.hadoop.dfs.Storage$StorageDirectory.analyzeStorage(Storage
> .java:264)
>         at org.apache.hadoop.dfs.DataStorage.recoverTransitionRead(DataStorage.j
> ava:83)
>         at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:230)
>         at org.apache.hadoop.dfs.DataNode.<init>(DataNode.java:199)
>         at org.apache.hadoop.dfs.DataNode.makeInstance(DataNode.java:1175)
>         at org.apache.hadoop.dfs.DataNode.run(DataNode.java:1119)
>         at org.apache.hadoop.dfs.DataNode.createDataNode(DataNode.java:1140)
>         at org.apache.hadoop.dfs.DataNode.main(DataNode.java:1299)

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

View raw message