You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2009/03/02 11:38:12 UTC

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

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

Hemanth Yamijala updated HADOOP-4744:
-------------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

I committed the latest patch to trunk and the 0.20 branch.

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