You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Xiaoyu Yao (JIRA)" <ji...@apache.org> on 2016/09/30 21:40:20 UTC
[jira] [Created] (HDFS-10941) Improve
BlockManager#processMisReplicatesAsync log
Xiaoyu Yao created HDFS-10941:
---------------------------------
Summary: Improve BlockManager#processMisReplicatesAsync log
Key: HDFS-10941
URL: https://issues.apache.org/jira/browse/HDFS-10941
Project: Hadoop HDFS
Issue Type: Improvement
Components: namenode
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
BlockManager#processMisReplicatesAsync is the daemon thread running inside namenode to handle miserplicated blocks. As shown below, it has a trace log for each of the block in the cluster being processed (10000 blocks per iteration after sleep 10s).
{code}
MisReplicationResult res = processMisReplicatedBlock(block);
if (LOG.isTraceEnabled()) {
LOG.trace("block " + block + ": " + res);
}
{code}
However, it is not very useful as dumping every block in the cluster will overwhelm the namenode log without much useful information assuming the majority of the blocks are not over/under replicated. This ticket is opened to improve the log for easy troubleshooting of block replication related issues by:
1) add debug log for blocks that get under/over replicated result during {{processMisReplicatedBlock()}}
2) or change to trace log for only blocks that get non-OK result during {{processMisReplicatedBlock()}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org