-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-32028][WEBUI] fix app id link for multi attempts app in history summary page #28867
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-32028][WEBUI] fix app id link for multi attempts app in history summary page #28867
Conversation
|
@dongjoon-hyun , @vanzin, @jerryshao , could you please help review this? |
|
ok to test |
|
Test build #124265 has finished for PR 28867 at commit
|
|
Retest this please. |
|
Test build #124303 has finished for PR 28867 at commit
|
core/src/main/resources/org/apache/spark/ui/static/historypage-template.html
Show resolved
Hide resolved
core/src/main/resources/org/apache/spark/ui/static/historypage-template.html
Show resolved
Hide resolved
|
@srowen , thank you for your reviewing. |
…y summary page ### What changes were proposed in this pull request? Fix app id link for multi attempts application in history summary page If attempt id is available (yarn), app id link url will contain correct attempt id, like `/history/application_1561589317410_0002/1/jobs/`. If attempt id is not available (standalone), app id link url will not contain fake attempt id, like `/history/app-20190404053606-0000/jobs/`. ### Why are the changes needed? This PR is for fixing [32028](https://issues.apache.org/jira/browse/SPARK-32028). App id link use application attempt count as attempt id. this would cause link url wrong for below cases: 1. there are multi attempts, all links point to last attempt  2. if there is one attempt, but attempt id is not 1 (before attempt maybe crash or fail to gerenerate event file). link url points to worng attempt (1) here.  ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? Tested this manually. Closes #28867 from zhli1142015/fix-appid-link-in-history-page. Authored-by: Zhen Li <[email protected]> Signed-off-by: Sean Owen <[email protected]> (cherry picked from commit eedc6cc) Signed-off-by: Sean Owen <[email protected]>
|
Merged to master/3.0 |
|
Hi, All. |
|
Yes could go back into 2.4.x. I'll try to cherry-pick. |
|
Thank you, @srowen ! |
…y summary page Fix app id link for multi attempts application in history summary page If attempt id is available (yarn), app id link url will contain correct attempt id, like `/history/application_1561589317410_0002/1/jobs/`. If attempt id is not available (standalone), app id link url will not contain fake attempt id, like `/history/app-20190404053606-0000/jobs/`. This PR is for fixing [32028](https://issues.apache.org/jira/browse/SPARK-32028). App id link use application attempt count as attempt id. this would cause link url wrong for below cases: 1. there are multi attempts, all links point to last attempt  2. if there is one attempt, but attempt id is not 1 (before attempt maybe crash or fail to gerenerate event file). link url points to worng attempt (1) here.  No Tested this manually. Closes apache#28867 from zhli1142015/fix-appid-link-in-history-page. Authored-by: Zhen Li <[email protected]> Signed-off-by: Sean Owen <[email protected]>
…istory summary page This is simply a backport of #28867 to branch-2.4 Closes #28949 from srowen/SPARK-32028.2. Authored-by: Zhen Li <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
What changes were proposed in this pull request?
Fix app id link for multi attempts application in history summary page
If attempt id is available (yarn), app id link url will contain correct attempt id, like
/history/application_1561589317410_0002/1/jobs/.If attempt id is not available (standalone), app id link url will not contain fake attempt id, like
/history/app-20190404053606-0000/jobs/.Why are the changes needed?
This PR is for fixing 32028. App id link use application attempt count as attempt id. this would cause link url wrong for below cases:
there are multi attempts, all links point to last attempt

if there is one attempt, but attempt id is not 1 (before attempt maybe crash or fail to gerenerate event file). link url points to worng attempt (1) here.

Does this PR introduce any user-facing change?
No
How was this patch tested?
Tested this manually.