Github user mccheah commented on the pull request:
https://github.com/apache/spark/pull/8007#issuecomment-132022341
Actually @markgrover can you describe in more detail how you were trying to
use GetExecutorLossReason? I think just using the code in this PR, my old
implementation should have still never called GetExecutorLossReason twice,
assuming that processing the RemoveExecutor event can never run in parallel
with processing the onDisconnected event. This new implementation is (IMO)
cleaner however in favoring the use of the Akka event loop a bit more instead
of the synchronized primitive.
---
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]
