GitHub user tejasapatil opened a pull request:

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

    [SPARK-17451] [CORE] CoarseGrainedExecutorBackend should inform driver 
before self-kill

    ## What changes were proposed in this pull request?
    
    Jira : https://issues.apache.org/jira/browse/SPARK-17451
    
    `CoarseGrainedExecutorBackend` in some failure cases exits the JVM. While 
this does not have any issue, from the driver UI there is no specific reason 
captured for this. In this PR, I am adding functionality to `exitExecutor` to 
notify driver that the executor is exiting.
    
    ## How was this patch tested?
    
    Ran the change over a test env and took down shuffle service before the 
executor could register to it. In the driver logs, where the job failure reason 
is mentioned (ie. `Job aborted due to stage ...` it gives the correct reason:
    
    Before:
    `ExecutorLostFailure (executor ZZZZZZZZZ exited caused by one of the 
running tasks) Reason: Remote RPC client disassociated. Likely due to 
containers exceeding thresholds, or network issues. Check driver logs for WARN 
messages.`
    
    After:
    `ExecutorLostFailure (executor ZZZZZZZZZ exited caused by one of the 
running tasks) Reason: Unable to create executor due to 
java.util.concurrent.TimeoutException: Timeout waiting for task.`

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

    $ git pull https://github.com/tejasapatil/spark SPARK-17451_inform_driver

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

    https://github.com/apache/spark/pull/15013.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 #15013
    
----
commit 5bd5534bf4397799f364f59a997d14a0f9ee6848
Author: Tejas Patil <tej...@fb.com>
Date:   2016-09-08T14:31:36Z

    [SPARK-17451] [CORE] CoarseGrainedExecutorBackend should inform driver 
before self-kill

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Reply via email to