[
https://issues.apache.org/jira/browse/HADOOP-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656125#action_12656125
]
Devaraj Das commented on HADOOP-4744:
-------------------------------------
Just to clarify things. The sequeunce of calls that are made are (details in
src/core/org/apache/hadoop/http/HttpServer.java) listed below. Please see if
something is missing or is incorrect in the sequence below.
{code}
Server webServer = new org.mortbay.jetty.Server();
Connector listener = new SelectChannelConnector();
listener.setLowResourceMaxIdleTime(10000);
listener.setAcceptQueueSize(128);
listener.setResolveNames(false);
listener.setUseDirectBuffers(false);
listener.setHost(bindAddress);
listener.setPort(port); //THE PORT PASSED IS 0
webServer.addConnector(listener);
//other webServer initialization follows...
//...
webServer.start();
port = webServer.getConnectors()[0].getLocalPort(); //CAN THIS RETURN -1
{code}
> 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.
