[
https://issues.apache.org/jira/browse/HADOOP-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677322#action_12677322
]
Greg Wilkins commented on HADOOP-4744:
--------------------------------------
Jothi,
latest patch looks about right.
However, it would be really interesting to include some logging in it to gather
a bit more information about the -1 return.
Specifically, I'm interested if the pause after an initial -1 return is
sufficient to get a non -1 port. If so, then there is
definitely a race or memory barrier problem within the JVM. If you you have
to close and reopen to be
successful, then something else is going on.
So I'd be hopeful this code will work around the issue, but as it is a kind of
ugly thing to do, it would be good to
find out more.
cheers
> 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, 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.
