GitHub user CodingCat opened a pull request:
https://github.com/apache/spark/pull/4063
[SPARK-5268] don't stop ExecutorBackend for irrelevant DisassociatedEvent
In CoarseGrainedExecutorBackend, we subscribe DisassociatedEvent in
executor backend actor and exit the program upon receive such event...
let's consider the following case
The user may develop an Akka-based program which starts the actor with
Spark's actor system and communicate with an external actor system (e.g. an
Akka-based receiver in spark streaming which communicates with an external
system) If the external actor system fails or disassociates with the actor
within spark's system with purpose, we may receive DisassociatedEvent and the
executor is restarted.
This is not the expected behavior.....
----
This is a simple fix to check the event before making the quit decision
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/CodingCat/spark SPARK-5268
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/4063.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 #4063
----
commit 4a65793563d14a85b37b5f90fea52b377aec2d5c
Author: CodingCat <[email protected]>
Date: 2015-01-15T15:17:33Z
check whether DisassociatedEvent is relevant before quit
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
