spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Cutler (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (SPARK-6980) Akka timeout exceptions indicate which conf controls them
Date Sat, 25 Apr 2015 00:10:38 GMT

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

Bryan Cutler updated SPARK-6980:
--------------------------------
    Comment: was deleted

(was: Modified ActorWordCount example to produce akka timeout)

> 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
>         Attachments: Spark-6980-Test.scala
>
>
> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message