hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-2661) Replicator log should include block id
Date Fri, 16 May 2008 22:31:55 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Raghu Angadi resolved HADOOP-2661.
----------------------------------

    Resolution: Fixed

This is part of HADOOP-3209.

> 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.


Mime
View raw message