hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4744) Wrong resolution of hostname and port
Date Mon, 23 Feb 2009 11:57:01 GMT

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

Devaraj Das commented on HADOOP-4744:
-------------------------------------

I just committed the workaround patch to the 0.20 and 0.21 branches but I am leaving the issue
open for now (with the hope that we will get a fix from the jetty folks). I am ignoring the
warning to do with invoking System.exit. 

> 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: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.20.0
>
>         Attachments: 4744.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.


Mime
View raw message