Github user GavinGavinNo1 commented on the pull request:
https://github.com/apache/spark/pull/10506#issuecomment-203702270
Thank you for your comment for PR #12054. I think changing app state from
WAITING to RUNNING in function completeRecovery. Suppose that some app is
WAITING before master toggle, then all apps and all workers get known of master
changed. But if last signal (WorkerSchedulerStateResponse or
MasterChangeAcknowledged) is from some worker, then function completeRecovery
is revoked, which means the app I mentioned above is in RUNNING state. If the
cluster doesn't have enough resource for all apps, maybe that app will be in a
wrong state for a while.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
