spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhihui (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SPARK-1946) Submit stage after executors have been registered
Date Wed, 28 May 2014 07:29:01 GMT

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

Zhihui updated SPARK-1946:
--------------------------

    Description: 
Because creating TaskSetManager and registering executors are asynchronous, in most situation,
early stages' tasks run without preferred locality.

A simple solution is sleeping few seconds in application, so that executors have enough time
to register.

A better way is to make DAGScheduler submit stage after a few of executors have been registered
by configuration properties.

\# submit stage only after successfully registered executors arrived the ratio, default value
0
spark.executor.registeredRatio = 0.8

\# whatever registeredRatio is arrived, submit stage after the maxRegisteredWaitingTime(millisecond),
default value 10000
spark.executor.maxRegisteredWaitingTime = 5000


  was:
Because creating TaskSetManager and registering executors are asynchronous, in most situation,
early stages' tasks run without preferred locality.

A simple solution is sleeping few seconds in application, so that executors have enough time
to register.

A better way is to make DAGScheduler submit stage after a few of executors have been registered
by configuration properties.

# submit stage only after successfully registered executors arrived the ratio, default value
0
spark.executor.registeredRatio = 0.8

# whatever registeredRatio is arrived, submit stage after the maxRegisteredWaitingTime(millisecond),
default value 10000
spark.executor.maxRegisteredWaitingTime = 5000



> Submit stage after executors have been registered
> -------------------------------------------------
>
>                 Key: SPARK-1946
>                 URL: https://issues.apache.org/jira/browse/SPARK-1946
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 1.0.0
>            Reporter: Zhihui
>         Attachments: Spark Task Scheduler Optimization Proposal.pptx
>
>
> Because creating TaskSetManager and registering executors are asynchronous, in most situation,
early stages' tasks run without preferred locality.
> A simple solution is sleeping few seconds in application, so that executors have enough
time to register.
> A better way is to make DAGScheduler submit stage after a few of executors have been
registered by configuration properties.
> \# submit stage only after successfully registered executors arrived the ratio, default
value 0
> spark.executor.registeredRatio = 0.8
> \# whatever registeredRatio is arrived, submit stage after the maxRegisteredWaitingTime(millisecond),
default value 10000
> spark.executor.maxRegisteredWaitingTime = 5000



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

Mime
View raw message