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 "Hairong Kuang (JIRA)" <ji...@apache.org> on 2006/05/04 03:49:18 UTC
[jira] Updated: (HADOOP-96) name server should log decisions that
affect data: block creation, removal, replication
[ http://issues.apache.org/jira/browse/HADOOP-96?page=all ]
Hairong Kuang updated HADOOP-96:
--------------------------------
Attachment: namenodeLogging.patch
Here is patch that includes the changes that Doug suggested. I tested it on a RH linux machine, it worked fine. But it seems that it has a problem on cygwin in that File.exists() returns true for a nonexistent directory. Doug, could you test it? If I am able to figure out what went wrong on cygwin, I will resubmit the patch tomorrow.
> name server should log decisions that affect data: block creation, removal, replication
> ---------------------------------------------------------------------------------------
>
> Key: HADOOP-96
> URL: http://issues.apache.org/jira/browse/HADOOP-96
> Project: Hadoop
> Type: Improvement
> Components: dfs
> Versions: 0.1.0
> Reporter: Yoram Arnon
> Assignee: Hairong Kuang
> Priority: Critical
> Fix For: 0.2
> Attachments: namenodeLogging.patch, namenodeLogging.patch
>
> currently, there's no way to analyze and debug DFS errors where blocks disapear.
> name server should log its decisions that affect data, including block creation, removal, replication:
> - block <b> created, assigned to datanodes A, B, ...
> - datanode A dead, block <b> underreplicated(1), replicating to datanode C
> - datanode B dead, block <b> underreplicated(2), replicating to datanode D
> - datanode A alive, block <b> overreplicated, removing from datanode D
> - block <removed> from datanodes C, D, ...
> that will enable me to track down, two weeks later, a block that's missing from a file, and to debug the name server.
> extra credit:
> - rotate log file, as it might grow large
> - make this behaviour optional/configurable
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira