GitHub user jiangxb1987 opened a pull request:

    https://github.com/apache/spark/pull/21915

    [SPARK-24954][Core] Fail fast on job submit if run a barrier stage with 
dynamic resource allocation enabled

    ## What changes were proposed in this pull request?
    
    We don't support run a barrier stage with dynamic resource allocation 
enabled, it shall lead to some confusing behaviors (eg. with dynamic resource 
allocation enabled, it may happen that we acquire some executors (but not 
enough to launch all the tasks in a barrier stage) and later release them due 
to executor idle time expire, and then acquire again).
    
    We perform the check on job submit and fail fast if running a barrier stage 
with dynamic resource allocation enabled.
    
    ## How was this patch tested?
    
    Added new test suite `BarrierStageOnSubmittedSuite` to cover all the fail 
fast cases that submitted a job containing one or more barrier stages.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jiangxb1987/spark SPARK-24954

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/21915.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #21915
    
----
commit 2ffa2b700eaf9913efd8de77e8194fa093d03581
Author: Xingbo Jiang <xingbo.jiang@...>
Date:   2018-07-30T14:34:48Z

    Fail fast on job submit if run a barrier stage with dynamic resource 
allocation enabled

----


---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to