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 "Hu Liu, (JIRA)" <ji...@apache.org> on 2014/10/24 08:53:33 UTC
[jira] [Updated] (HDFS-7284) Add more debug info to
BlockInfoUnderConstruction#setGenerationStampAndVerifyReplicas
[ https://issues.apache.org/jira/browse/HDFS-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hu Liu, updated HDFS-7284:
--------------------------
Issue Type: Improvement (was: Bug)
> Add more debug info to BlockInfoUnderConstruction#setGenerationStampAndVerifyReplicas
> -------------------------------------------------------------------------------------
>
> Key: HDFS-7284
> URL: https://issues.apache.org/jira/browse/HDFS-7284
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 2.5.1
> Reporter: Hu Liu,
>
> When I was looking at some replica loss issue, I got the following info from log
> {code}
> 2014-10-13 01:54:53,104 INFO BlockStateChange: BLOCK* Removing stale replica from location x.x.x.x
> {code}
> I could just know that a replica is removed, but I don't know which block and its timestamp. I need to know the id and timestamp of the block from the log file.
> So it's better to add more info including block id and timestamp to the code snippet
> {code}
> for (ReplicaUnderConstruction r : replicas) {
> if (genStamp != r.getGenerationStamp()) {
> r.getExpectedLocation().removeBlock(this);
> NameNode.blockStateChangeLog.info("BLOCK* Removing stale replica "
> + "from location: " + r.getExpectedLocation());
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)