[ 
https://issues.apache.org/jira/browse/HDFS-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033368#comment-13033368
 ] 

Todd Lipcon commented on HDFS-1332:
-----------------------------------

Just a sample of why this JIRA is important, from #hadoop IRC a minute ago:
{code}
15:23 < user> Hi all. I have a strange problem - I can't seem to run a simple 
copyFromLocal command from 
                      my local machine, but everything works fine if i log into 
the master as the same user and 
                      issue command
15:25 < user> the error it throws is cryptic - java.io.IOException: File 
/foo/bar could only be 
                      replicated to 0 nodes, instead of 1
15:26 < user> i checked the namenode and tasktracker logs - nothing of interest 
there (except the error i 
                      mentioned, of course)
{code}

> When unable to place replicas, BlockPlacementPolicy should log reasons nodes 
> were excluded
> ------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1332
>                 URL: https://issues.apache.org/jira/browse/HDFS-1332
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>            Reporter: Todd Lipcon
>            Assignee: Ted Yu
>            Priority: Minor
>              Labels: newbie
>             Fix For: 0.23.0
>
>         Attachments: HDFS-1332.patch
>
>
> Whenever the block placement policy determines that a node is not a "good 
> target" it could add the reason for exclusion to a list, and then when we log 
> "Not able to place enough replicas" we could say why each node was refused. 
> This would help new users who are having issues on pseudo-distributed (eg 
> because their data dir is on /tmp and /tmp is full). Right now it's very 
> difficult to figure out the issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to