[
https://issues.apache.org/jira/browse/HADOOP-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655719#action_12655719
]
Devaraj Das commented on HADOOP-4744:
-------------------------------------
Observed that this happens whenever the HttpServer.getPort() (that internally
calls webServer.getConnectors()[0].getLocalPort()) returns a -1. In the
TaskTracker logs for this particular node, it seems jetty could successfully
bind to a valid port. The question is why would jetty return a -1 when it is
queried. Could it be a race condition in jetty to do with storing the port
number in a particular field. Or, does jetty bind to the port asynchronously
(putting it in another way, is webServer.start a blocking call) ? Note that we
are passing 0 as the port# to bind to, which means it should bind to an OS
assigned port...
> 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
> Priority: Blocker
> Fix For: 0.20.0
>
>
> 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.
