hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Chansler (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2917) java.net.SocketTimeoutException: timed out waiting for rpc response
Date Fri, 29 Feb 2008 19:48:51 GMT

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

Robert Chansler updated HADOOP-2917:
------------------------------------

    Component/s: dfs

> java.net.SocketTimeoutException: timed out waiting for rpc response 
> --------------------------------------------------------------------
>
>                 Key: HADOOP-2917
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2917
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.16.0
>         Environment: Pig
>            Reporter: Amir Youssefi
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message