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
Reporter: Yoram Arnon
Priority: Critical
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
