Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/10794#issuecomment-186128437
@jerryshao when yarn-client, because driver is always running, when AM
failure occurs, some executors that is created by previous AM may still exist
after second AM start. so I think we need to reset in
CoarseGrainedSchedulerBackend that can remove all historical executors before
second AM allocate new executors.
---
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]
