[
https://issues.apache.org/jira/browse/HADOOP-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706788#action_12706788
]
Steve Loughran commented on HADOOP-4744:
----------------------------------------
Could the new patch throw an exception instead? As the hadoop-4744-new.patch
did? That means that however the TT is executed -and that included under junit-
the failure is caught at the right layer of code, instead of having methods
acrosss the codebase deciding when to exit the JVM.
> Wrong resolution of hostname and port
> --------------------------------------
>
> Key: HADOOP-4744
> URL: https://issues.apache.org/jira/browse/HADOOP-4744
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Amareshwari Sriramadasu
> Assignee: Jothi Padmanabhan
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: 4744.exception.patch, 4744.patch, 4744.reopened.patch,
> hadoop-4744-new.patch
>
>
> I noticed the following for one of the hosts in a cluster:
> 1. machines.jsp page resolves the http address as just "http://hostname";
> (which doesn't work). It doesnt put the port number for the host. Even if I
> add the port number manually in the URI, the task tracker page does not come
> up.
> 2. All the tasks(both maps and reduces) which ran on the machine ran
> successfully. But tasklogs cannot be viewed, because port-number is not
> resolved. ( same problem as in (1)).
> 3. The reducers waiting for maps ran on that machine fail with connection
> failed errors saying the hostname is 'null'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
