[ http://issues.apache.org/jira/browse/HADOOP-19?page=all ]

Doug Cutting resolved HADOOP-19:

Resolution: Fixed

I added a format command to namenode. Now one must run 'bin/hadoop namenode -format' whenever a new dfs.data.dir is configured. A misconfigured namenode will thus no longer create a new empty filesystem and then tell all datanodes to discard their blocks.
Datanode corruption

Key: HADOOP-19
URL: http://issues.apache.org/jira/browse/HADOOP-19
Project: Hadoop
Type: Bug
Components: dfs
Versions: 0.1
Reporter: Rod Taylor
Assignee: Doug Cutting
Priority: Critical
Fix For: 0.1
Our admins accidentally started a second nutch datanode pointing to the same directories as one already running (same machine) which in turn caused the entire contents of the datanode to go disappear.
This happened because the blocking was based on the username (since fixed in our start scripts) and it was started as two different users.
The ndfs.name.dir and ndfs.data.dir directories were both completely devoid of content, where they had about 150GB not all that much earlier.
I think the solution is improved interlocking within the data directory itself (file locked with flock or something similar).
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
postedMar 28, '06 at 6:18p
activeMar 28, '06 at 6:18p

1 user in discussion

Doug Cutting (JIRA): 1 post



site design / logo © 2022 Grokbase