Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <2079203.1188242610964.JavaMail.jira@brutus>
Date: Mon, 27 Aug 2007 12:23:30 -0700 (PDT)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-1739) ConnectException in TaskTracker Child
In-Reply-To: <18467997.1187648970596.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arun C Murthy updated HADOOP-1739:
----------------------------------

    Priority: Major  (was: Blocker)

Since this can be fixed right-away by setting {{mapred.tracker.report.port}} to *zero* (there-by simulating the patch); and given the ambiguity about how to fix (or remove) {{@port@}} which depends on this, I'm marking this as a non-blocker.

> ConnectException in TaskTracker Child
> -------------------------------------
>
>                 Key: HADOOP-1739
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1739
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.14.0
>         Environment: Version: 0.15.0-dev, r565628
> Compiled: Tue Aug 14 20:55:37 UTC 2007 by hadoopqa
> 1400 nodes
>            Reporter: Srikanth Kakani
>            Assignee: Arun C Murthy
>             Fix For: 0.15.0
>
>         Attachments: HADOOP-1739_1_20070823.patch, HADOOP-1739_2_20070825.patch
>
>
> Steps to Reproduce:
> I had 11000 mappers and 2700 reducers in a job and most failures correspond to the following logs:
> Stderr:
> Exception in thread "main" java.net.ConnectException: Connection refused
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:193)
> 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> 	at java.net.Socket.connect(Socket.java:519)
> 	at org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:150)
> 	at org.apache.hadoop.ipc.Client.getConnection(Client.java:530)
> 	at org.apache.hadoop.ipc.Client.call(Client.java:459)
> 	at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:165)
> 	at org.apache.hadoop.mapred.$Proxy0.getProtocolVersion(Unknown Source)
> 	at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:248)
> 	at org.apache.hadoop.mapred.TaskTracker$Child.main(TaskTracker.java:1781)
> Syslog:
> 2007-08-19 18:45:07,490 INFO org.apache.hadoop.ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:50051. Already tried 1 time(s).
> 2007-08-19 18:45:08,494 INFO org.apache.hadoop.ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:50051. Already tried 2 time(s).
> 2007-08-19 18:45:09,497 INFO org.apache.hadoop.ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:50051. Already tried 3 time(s).
> 2007-08-19 18:45:10,500 INFO org.apache.hadoop.ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:50051. Already tried 4 time(s).
> 2007-08-19 18:45:11,503 INFO org.apache.hadoop.ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:50051. Already tried 5 time(s).
> 2007-08-19 18:45:12,506 INFO org.apache.hadoop.ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:50051. Already tried 6 time(s).
> 2007-08-19 18:45:13,508 INFO org.apache.hadoop.ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:50051. Already tried 7 time(s).
> 2007-08-19 18:45:14,511 INFO org.apache.hadoop.ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:50051. Already tried 8 time(s).
> 2007-08-19 18:45:15,512 INFO org.apache.hadoop.ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:50051. Already tried 9 time(s).
> 2007-08-19 18:45:16,515 INFO org.apache.hadoop.ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:50051. Already tried 10 time(s)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.