Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/18663#discussion_r128091929
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/scheduler/cluster/YarnSchedulerBackend.scala
---
@@ -262,13 +259,7 @@ private[spark] abstract class YarnSchedulerBackend(
case RegisterClusterManager(am) =>
logInfo(s"ApplicationMaster registered as $am")
amEndpoint = Option(am)
- if (!shouldResetOnAmRegister) {
- shouldResetOnAmRegister = true
- } else {
- // AM is already registered before, this potentially means that
AM failed and
- // a new one registered after the failure. This will only happen
in yarn-client mode.
- reset()
- }
+ reset()
--- End diff --
Thanks for the explain, let me try your patch locally.
---
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]
