GitHub user WangTaoTheTonic opened a pull request: https://github.com/apache/spark/pull/14605
[SPARK-17022][YARN]Handle potential deadlock in driver handling messages ## What changes were proposed in this pull request? We directly send RequestExecutors to AM instead of transfer it to yarnShedulerBackend first. ## How was this patch tested? manual tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/WangTaoTheTonic/spark lock Alternatively you can review and apply these changes as the patch at: https://github.com/apache/spark/pull/14605.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 #14605 ---- commit 80c2d1127318f1315c7ba59bc42162c757f08c73 Author: WangTaoTheTonic <wangtao...@huawei.com> Date: 2016-08-11T15:49:03Z [SPARK-17022]Handle potential deadlock in driver handling messages ---- --- 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