[
https://issues.apache.org/jira/browse/HADOOP-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560046#action_12560046
]
Raghu Angadi commented on HADOOP-290:
-------------------------------------
+1. finnally this is getting fixed :). There are a few more quirks with
Datanode logging. I will file a different jira later.
> Fix Datanode transfer thread logging
> ------------------------------------
>
> Key: HADOOP-290
> URL: https://issues.apache.org/jira/browse/HADOOP-290
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.4.0
> Environment: linux, java 1.5
> Reporter: Dennis Kubes
> Assignee: dhruba borthakur
> Priority: Minor
> Attachments: logging_patch, logging_patch2,
> transferLoggingMessage.patch, transferLoggingMessage.patch,
> transferLoggingMessage.patch, transferLoggingMessage.patch
>
>
> Under the current datanode the logging of "Starting thread to transfer block"
> doesn't print out the hosts that it is transferring to, it prints out a java
> array toString. This patch fixes this and prints out the hostnames and ports
> for all hosts we are tranferring to.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
