You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Mark Hamstra (JIRA)" <ji...@apache.org> on 2014/05/05 22:41:14 UTC

[jira] [Commented] (SPARK-1715) Ensure actor is self-contained in DAGScheduler

    [ https://issues.apache.org/jira/browse/SPARK-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989940#comment-13989940 ] 

Mark Hamstra commented on SPARK-1715:
-------------------------------------

This shouldn't involve any change to the public API, so we should be able to do it already in 1.0.1.

> Ensure actor is self-contained in DAGScheduler
> ----------------------------------------------
>
>                 Key: SPARK-1715
>                 URL: https://issues.apache.org/jira/browse/SPARK-1715
>             Project: Spark
>          Issue Type: Bug
>            Reporter: Nan Zhu
>            Assignee: Nan Zhu
>             Fix For: 1.0.1
>
>
> Though the current supervisor-child structure works fine for fault-tolerance, it violates the basic rule that the actor is better to be self-contained
> We should forward the message from supervisor to the child actor, so that we can eliminate the hard-coded timeout threshold for starting the DAGScheduler and provide more convenient interface for future development like parallel DAGScheduler, or new changes to the DAGScheduler



--
This message was sent by Atlassian JIRA
(v6.2#6252)