GitHub user markhamstra opened a pull request:
https://github.com/apache/spark/pull/3550
[SPARK-4498][core] Don't transition ExecutorInfo to RUNNING until Driver
adds Executor
The ExecutorInfo only reaches the RUNNING state if the Driver is alive to
send the ExecutorStateChanged message to master. Else,
appInfo.resetRetryCount() is never called and failing Executors will eventually
exceed ApplicationState.MAX_NUM_RETRY, resulting in the application being
removed from the master's accounting.
@JoshRosen
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markhamstra/spark SPARK-4498
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/3550.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 #3550
----
commit 8f543b10222bf5006326d3fe0605d54474175501
Author: Mark Hamstra <markhams...@gmail.com>
Date: 2014-12-02T06:54:07Z
Don't transition ExecutorInfo to RUNNING until Executor is added by Driver
----
---
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
