[
https://issues.apache.org/jira/browse/SPARK-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512069#comment-14512069
]
Bryan Cutler commented on SPARK-6980:
-------------------------------------
I'm working out of trunk.
Changing the ActorWordCount example to perform an ask/reply sequence using
AkkaUtils.askWithReply, I'm able to get a timeout (below), but it is also
preceded by a warning that describes the failed message - so I'm not sure if
this is the same use case described by [~imranr].
{noformat}
15/04/24 16:33:52 WARN AkkaUtils: Error sending message [message = requesting
words] in 1 attempts
java.util.concurrent.TimeoutException: Futures timed out after [1000
milliseconds]
at scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:219)
at
scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:223)
at scala.concurrent.Await$$anonfun$result$1.apply(package.scala:107)
at
scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:53)
at scala.concurrent.Await$.result(package.scala:107)
at org.apache.spark.util.AkkaUtils$.askWithReply(AkkaUtils.scala:195)
at org.apache.spark.util.AkkaUtils$.askWithReply(AkkaUtils.scala:171)
at
org.apache.spark.examples.streaming.AskWithReplyActor$$anon$2.run(Spark-6980-Test.scala:107)
{noformat}
So my questions are:
# Is there another way to use akka in Spark streaming that could lead to a
timeout that *doesn't* make use of AkkaUtils.askWithReply?
# If not, does it make sense to just elaborate in the exception thrown in
AkkaUtils.askWithReply?
I'm attaching the modified ActorWordCount test..
> Akka timeout exceptions indicate which conf controls them
> ---------------------------------------------------------
>
> Key: SPARK-6980
> URL: https://issues.apache.org/jira/browse/SPARK-6980
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Reporter: Imran Rashid
> Assignee: Harsh Gupta
> Priority: Minor
> Labels: starter
>
> If you hit one of the akka timeouts, you just get an exception like
> {code}
> java.util.concurrent.TimeoutException: Futures timed out after [30 seconds]
> {code}
> The exception doesn't indicate how to change the timeout, though there is
> usually (always?) a corresponding setting in {{SparkConf}} . It would be
> nice if the exception including the relevant setting.
> I think this should be pretty easy to do -- we just need to create something
> like a {{NamedTimeout}}. It would have its own {{await}} method, catches the
> akka timeout and throws its own exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
