[ http://issues.apache.org/jira/browse/HADOOP-96?page=comments#action_12377261 ]
Hairong Kuang commented on HADOOP-96: ------------------------------------- Yes, it makes sense to log the log file name. I will make the change. If HADOOP_LOG_DIR is set, the log directory is set to be HADOOP_LOG_DIR. Otherwise, if HADOOP_HOME is set, the log directory is set to be HADOOP_HOME/logs. Otherwise, it is set to be the user's home directory. I do not know why you saw log files in HADOOP_HOME. I will take a look. > 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
