[ http://issues.apache.org/jira/browse/HADOOP-96?page=all ]
Hairong Kuang updated HADOOP-96:
--------------------------------
Attachment: namenodeLogging.patch
This patch adds the following features
1. NameNode adds a static field "stateChangeLog" that keeps tracks of all the
namenode state changes
2. Various logging statements are added to NameNode, FSNamesystem, FSDirectory.
Basically namesapce (dir) changes are logged at the fine level and block
changes are logged at the finer level
3. initFileHandler is added to LogFormatter. All logs are directed to a log
file instead of stdout. All logs are rolled and capped in size. Log file names
end with .log.
4. In hadoop-daemon.sh, stdout is redirected to a .out file.
5. namenode logging levels, log file max size, and number of generations are
configurable.
6. A JUnit test program is added to test the correctness of namespace change
logging.
> 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
>
> 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
