[jira] Updated: (HADOOP-4744) Wrong resolution of hostname and port

["Devaraj Das (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Devaraj Das updated HADOOP-4744:
--------------------------------

    Attachment: 4744.reopened.patch

Looks like the jetty bounce code is not working as expected. Specifically, this is what is observed:
1) In HttpServer.java::start(), after the call to listener.open(), the listener.getLocalPort() returns a seemingly right port number
2) After the above, in TaskTracker.java, the call to HttpServer.getPort() returns a -1. (HttpServer.getPort() invokes listener.getLocalPort() indirectly)

When this happens, we manually checked whether jetty actually bound to the port that it claimed in (1), and we saw that jetty didn't bind to any port at all! So it is a complete mystery how the call getLocalPort could return two different values at two different times. 

This patch tries to work around the problem by shutting down the TaskTracker process if and when (2) happens. 

> 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.