You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Robert Chansler (JIRA)" <ji...@apache.org> on 2008/03/25 04:03:26 UTC
[jira] Updated: (HADOOP-2661) Replicator log should include block
id
[ https://issues.apache.org/jira/browse/HADOOP-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Chansler updated HADOOP-2661:
------------------------------------
Fix Version/s: (was: 0.17.0)
> Replicator log should include block id
> --------------------------------------
>
> Key: HADOOP-2661
> URL: https://issues.apache.org/jira/browse/HADOOP-2661
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.15.0
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
> Priority: Minor
>
> Currently when Replicator can not find datanodes to place required replications for a block, it does not print the actual block id. Block id would help while debugging problems similar to http://www.nabble.com/Under-replicated-block-doesn't-get-fixed-until-DFS-restart-td14624430.html , HADOOP-2201.
> log from trunk currently looks like :
> {noformat} 2007-11-13 22:08:40,727 WARN fs.FSNamesystem (ReplicationTargetChooser.java:chooseTarget(177)) -
> Not able to place enough replicas, still in need of 1 {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.