[
https://issues.apache.org/jira/browse/SPARK-18554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15694563#comment-15694563
]
Saisai Shao commented on SPARK-18554:
-------------------------------------
I think this is a known issue and I have a fix for it long long ago
(https://github.com/apache/spark/pull/10506), but still pending.
> leader master lost the leadership, when the slave become master, the
> perivious app's state display as waitting
> --------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-18554
> URL: https://issues.apache.org/jira/browse/SPARK-18554
> Project: Spark
> Issue Type: Bug
> Components: Deploy, Web UI
> Affects Versions: 1.6.1
> Environment: java1.8
> Reporter: liujianhui
> Priority: Minor
>
> when the leader of master lost the leadship and the slave become master, the
> state of app in the webui will display waiting; this code as follow
> case MasterChangeAcknowledged(appId) => {
> idToApp.get(appId) match {
> case Some(app) =>
> logInfo("Application has been re-registered: " + appId)
> app.state = ApplicationState.WAITING
> case None =>
> logWarning("Master change ack from unknown app: " + appId)
> }
> if (canCompleteRecovery) { completeRecovery() }
> the state of app should be RUNNING instead of waiting
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
