-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-4411][UI]Add kill link for jobs in the UI #4823
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
Conversation
|
Test build #28107 has started for PR 4823 at commit
|
|
Test build #28107 has finished for PR 4823 at commit
|
|
Test PASSed. |
|
Test build #28112 has started for PR 4823 at commit
|
|
Test build #28112 has finished for PR 4823 at commit
|
|
Test PASSed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few tiny comments to consider, if you have to otherwise make changes to this PR: this might be easier to read with string interpolation
|
Test build #28140 has started for PR 4823 at commit
|
|
@srowen i have update for your comments. can you take a look again. thanks. |
|
Test build #28142 has started for PR 4823 at commit
|
|
Test build #28140 has finished for PR 4823 at commit
|
|
Test FAILed. |
|
Test build #28142 has finished for PR 4823 at commit
|
|
Test PASSed. |
|
OK by me; would be good to let @kayousterhout give it a thumbs up. |
|
@JoshRosen @kayousterhout what do you think |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add : Unit return type here (and other places)
|
Test build #29064 has started for PR 4823 at commit
|
|
Test build #29064 has finished for PR 4823 at commit
|
|
Test PASSed. |
|
Test build #29135 has started for PR 4823 at commit
|
|
Test build #29135 has finished for PR 4823 at commit
|
|
Test FAILed. |
|
I think this would have to be rebased at least, and rewritten to match the new kill link behavior elsewhere. Can this be closed? |
## What changes were proposed in this pull request? Currently users can kill stages via the web ui but not jobs directly (jobs are killed if one of their stages is). I've added the ability to kill jobs via the web ui. This code change is based on apache#4823 by lianhuiwang and updated to work with the latest code matching how stages are currently killed. In general I've copied the kill stage code warning and note comments and all. I also updated applicable tests and documentation. ## How was this patch tested? Manually tested and dev/run-tests  Author: Alex Bozarth <[email protected]> Author: Lianhui Wang <[email protected]> Closes apache#15441 from ajbozarth/spark4411.
## What changes were proposed in this pull request? Currently users can kill stages via the web ui but not jobs directly (jobs are killed if one of their stages is). I've added the ability to kill jobs via the web ui. This code change is based on apache#4823 by lianhuiwang and updated to work with the latest code matching how stages are currently killed. In general I've copied the kill stage code warning and note comments and all. I also updated applicable tests and documentation. ## How was this patch tested? Manually tested and dev/run-tests  Author: Alex Bozarth <[email protected]> Author: Lianhui Wang <[email protected]> Closes apache#15441 from ajbozarth/spark4411.
## What changes were proposed in this pull request? Currently users can kill stages via the web ui but not jobs directly (jobs are killed if one of their stages is). I've added the ability to kill jobs via the web ui. This code change is based on apache#4823 by lianhuiwang and updated to work with the latest code matching how stages are currently killed. In general I've copied the kill stage code warning and note comments and all. I also updated applicable tests and documentation. ## How was this patch tested? Manually tested and dev/run-tests  Author: Alex Bozarth <[email protected]> Author: Lianhui Wang <[email protected]> Closes apache#15441 from ajbozarth/spark4411.
We should have a "kill" link for each job, similar to what we have for each stage, so it's easier for users to kill jobs in the UI. @kayousterhout can you take a look at this? thanks.