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

["Jothi Padmanabhan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660266#action_12660266 ] 

Jothi Padmanabhan commented on HADOOP-4744:
-------------------------------------------

I printed the port number returned by getPort (which internally calls getLocalPort) in TaskTracker.java after we do the server.start. It did print -1.  A brief perusal of  org.mortbay.jetty.Server.java shows that connectors.start is called from inside server.start. David/Greg, could you confirm if  this  is correct?  Is there some timing issue involved somewhere where the port is still not set before the Server.start is returned? 

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