[
https://issues.apache.org/jira/browse/HDFS-16870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18033726#comment-18033726
]
ASF GitHub Bot commented on HDFS-16870:
---------------------------------------
github-actions[bot] commented on PR #5237:
URL: https://github.com/apache/hadoop/pull/5237#issuecomment-3459165671
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> 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
> Labels: pull-request-available
>
> 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
> address 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: [email protected]
For additional commands, e-mail: [email protected]
