[
https://issues.apache.org/jira/browse/HDFS-16870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Ma updated HDFS-16870:
-----------------------------
Description:
There are two scenario involved for reportBadBlocks.
1-HDFS client will report bad block to NameNode once the block size is
inconsitent with meta;
2-DataNode will report bad block to NameNode via heartbeat if Replica stored on
DataNode is corrupted or be modified.
Currently, when namenode process reportBadBlock rpc request, only DataNode Ip
is recorded in Log msg,
Client Ip should also be recorded to distinguish where the report comes from,
which is very useful for trouble shooting.
> Client ip should also be recorded when NameNode is processing reportBadBlocks
> -----------------------------------------------------------------------------
>
> Key: HDFS-16870
> URL: https://issues.apache.org/jira/browse/HDFS-16870
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Daniel Ma
> Priority: Trivial
>
> There are two scenario involved for reportBadBlocks.
> 1-HDFS client will report bad block to NameNode once the block size is
> inconsitent with meta;
> 2-DataNode will report bad block to NameNode via heartbeat if Replica stored
> on DataNode is corrupted or be modified.
> Currently, when namenode process reportBadBlock rpc request, only DataNode Ip
> is recorded in Log msg,
> Client Ip should also be recorded to distinguish where the report comes from,
> which is very useful for trouble shooting.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
