hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-191) java.net.SocketTimeoutException: timed out waiting for rpc response
Date Wed, 25 Jan 2012 21:35:38 GMT

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

Suresh Srinivas resolved HDFS-191.
----------------------------------

    Resolution: Won't Fix

This is an old bug. Lot of things have changed since this bug has been filed. Please open
another bug, if this problem is still seen.
                
> java.net.SocketTimeoutException: timed out waiting for rpc response 
> --------------------------------------------------------------------
>
>                 Key: HDFS-191
>                 URL: https://issues.apache.org/jira/browse/HDFS-191
>             Project: Hadoop HDFS
>          Issue Type: Bug
>         Environment: Pig
>            Reporter: Amir Youssefi
>            Priority: Critical
>
> Following exception happens when users run Pig queries over large data. Brought up this
with Hadoop team and this is follow-up JIRA. 
> java.net.SocketTimeoutException: timed out waiting for rpc response
>         at org.apache.hadoop.ipc.Client.call(Client.java:484)
>         at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:184)
>         at $Proxy1.getJobStatus(Unknown Source)
>         at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:82)
>         at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:59)
>         at $Proxy1.getJobStatus(Unknown Source)
>         at org.apache.hadoop.mapred.JobClient$NetworkedJob.ensureFreshStatus(JobClient.java:182)
>         at org.apache.hadoop.mapred.JobClient$NetworkedJob.isComplete(JobClient.java:237)
>         at org.apache.pig.impl.mapreduceExec.MapReduceLauncher.launchPig(MapReduceLauncher.java:189)
>         at org.apache.pig.impl.physicalLayer.POMapreduce.open(POMapreduce.java:136)
>         at org.apache.pig.impl.physicalLayer.PhysicalPlan.exec(PhysicalPlan.java:39)
>         at org.apache.pig.impl.physicalLayer.IntermedResult.exec(IntermedResult.java:122)
>         at org.apache.pig.PigServer.store(PigServer.java:445)
>         at org.apache.pig.PigServer.store(PigServer.java:413)
>         at org.apache.pig.tools.grunt.GruntParser.processStore(GruntParser.java:135)
>         at org.apache.pig.tools.pigscript.parser.PigScriptParser.parse(PigScriptParser.java:327)
>         at org.apache.pig.tools.grunt.GruntParser.parseContOnError(GruntParser.java:64)
>         at org.apache.pig.tools.grunt.Grunt.run(Grunt.java:48)
>         at org.apache.pig.Main.main(Main.java:246)
> timed out waiting for rpc response
> Is this a bug or we have  a time-out setting directly related to this in Hadoop?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message