You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Todd Lipcon (Updated) (JIRA)" <ji...@apache.org> on 2012/02/22 22:31:48 UTC
[jira] [Updated] (HDFS-2985) Improve logging when replicas are
marked as corrupt
[ https://issues.apache.org/jira/browse/HDFS-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HDFS-2985:
------------------------------
Attachment: hdfs-2985.txt
Attached patch improves the logging, eg from one of the unit tests:
2012-02-22 13:23:46,673 INFO hdfs.StateChange (CorruptReplicasMap.java:addToCorruptReplicasMap(66)) - BLOCK NameSystem.addToCorruptReplicasMap: blk_-3366668708952852382 added as corrupt on 127.0.0.1:36824 by null because block is COMPLETE and reported genstamp -5648172540531912512 does not match genstamp in block map 1001
> Improve logging when replicas are marked as corrupt
> ---------------------------------------------------
>
> Key: HDFS-2985
> URL: https://issues.apache.org/jira/browse/HDFS-2985
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Attachments: hdfs-2985.txt
>
>
> Currently in 0.23 and trunk, there is no logging which indicates _why_ a replica has been marked corrupt, only that it has been marked corrupt. Because corruption can be a serious problem (and should be very rare), it's worth logging more detail whenever a block is added to the corrupt replica map.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira