[
https://issues.apache.org/jira/browse/SPARK-13675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao updated SPARK-13675:
--------------------------------
Description:
Current URL for each application to access history UI is like:
http://localhost:18080/history/application_1457058760338_0016/1/jobs/ or
http://localhost:18080/history/application_1457058760338_0016/2/jobs/
Here *1* or *2* represents the number of attempts in {{historypage.js}}, but it
will parse to attempt id in {{HistoryServer}}, while the correct attempt id
should be like "appattempt_1457058760338_0016_000002", so it will fail to parse
to a correct attempt id in {{HistoryServer}}.
This is OK in yarn client mode, since we don't need this attempt id to fetch
out the app cache, but it is failed in yarn cluster mode, where attempt id "1"
or "2" is actually wrong.
So here we should fix this url to parse the correct application id and attempt
id.
This bug is newly introduced in SPARK-10873, there's no issue in branch 1.6.
Here is the screenshot:
!https://issues.apache.org/jira/secure/attachment/12791437/Screen%20Shot%202016-02-29%20at%203.57.32%20PM.png!
was:
Current URL for each application to access history UI is like:
http://localhost:18080/history/application_1457058760338_0016/1/jobs/ or
http://localhost:18080/history/application_1457058760338_0016/2/jobs/
Here *1* or *2* represents the number of attempts in {{historypage.js}}, but it
will parse to attempt id in {{HistoryServer}}, while the correct attempt id
should be like "appattempt_1457058760338_0016_000002", so it will fail to parse
to a correct attempt id in {{HistoryServer}}.
This is OK in yarn client mode, since we don't need this attempt id to fetch
out the app cache, but it is failed in yarn cluster mode, where attempt id "1"
or "2" is actually wrong.
So here we should fix this url to parse the correct application id and attempt
id.
This bug is newly introduced in SPARK-10873, there's no issue in branch 1.6.
> The url link in historypage is not correct for application running in yarn
> cluster mode
> ---------------------------------------------------------------------------------------
>
> Key: SPARK-13675
> URL: https://issues.apache.org/jira/browse/SPARK-13675
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 2.0.0
> Reporter: Saisai Shao
> Attachments: Screen Shot 2016-02-29 at 3.57.32 PM.png
>
>
> Current URL for each application to access history UI is like:
> http://localhost:18080/history/application_1457058760338_0016/1/jobs/ or
> http://localhost:18080/history/application_1457058760338_0016/2/jobs/
> Here *1* or *2* represents the number of attempts in {{historypage.js}}, but
> it will parse to attempt id in {{HistoryServer}}, while the correct attempt
> id should be like "appattempt_1457058760338_0016_000002", so it will fail to
> parse to a correct attempt id in {{HistoryServer}}.
> This is OK in yarn client mode, since we don't need this attempt id to fetch
> out the app cache, but it is failed in yarn cluster mode, where attempt id
> "1" or "2" is actually wrong.
> So here we should fix this url to parse the correct application id and
> attempt id.
> This bug is newly introduced in SPARK-10873, there's no issue in branch 1.6.
> Here is the screenshot:
> !https://issues.apache.org/jira/secure/attachment/12791437/Screen%20Shot%202016-02-29%20at%203.57.32%20PM.png!
--
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
