Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9963#discussion_r46458512
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/YarnSchedulerBackend.scala
---
@@ -168,6 +178,13 @@ private[spark] abstract class YarnSchedulerBackend(
logInfo(s"ApplicationMaster registered as $am")
amEndpoint = Option(am)
+ case ReregisterClusterManager(am) =>
--- End diff --
> Is it robust enough to use amEndpoint to distinguish whether AM is
registered again or not?
That's the same that would happen if you have a 3rd attempt of running the
AM. So better to handle registration the same way for all attempts.
---
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]
