[
https://issues.apache.org/jira/browse/HDFS-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035062#comment-13035062
]
Tsz Wo (Nicholas), SZE commented on HDFS-1332:
----------------------------------------------
Thanks Ted,
- This part looks mysterious. Since the entire theme of this issue is for
support new users, they may ask "Why it only can be replicated to 0 nodes but
there is 1 datanode?"
{noformat}
... File /filestatus.dat could only be replicated to 0 nodes, instead of 1,
because there are 1 datanodes running.
{noformat}
- We only have to append the {{failingReason}} to the string builder. The log
should be removed, otherwise, we will have repeated messages.
{noformat}
+ FSNamesystem.LOG.debug(failingReason);
{noformat}
> 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-concise.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
