Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/5018#issuecomment-82024746
+1 to this code being confusing and overly complicated. There are 3 places
tracking executor state (ExecutorAllocationManager,
CoarseGrainedSchedulerBackend and YarnAllocator), not to mention all the other
places where the RPCs are plumbed through. It's a maze just to find out what
calls out to what, and which is the right state at any moment.
But the patch is targeted at fixing the bug and being as non-intrusive as
possible.
---
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]
