Skip to content
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-12716] [Web UI] Add a TOTALS row to the Executors Web UI #10668

Closed
wants to merge 6 commits into from

Conversation

ajbozarth
Copy link
Member

Added a Totals table to the top of the page to display the totals of each applicable column in the executors table.

Old Description:
Created a TOTALS row containing the totals of each column in the executors UI. By default the TOTALS row appears at the top of the table. When a column is sorted the TOTALS row will always sort to either the top or bottom of the table.

@ajbozarth
Copy link
Member Author

Screenshots:
Initial page load
initial
Sort by address
sortaddrbottom
sortaddrtop
Sort by ID
sortidbottom
sortidtop
Sort by Task Count
sorttasksbottom
sorttaskstop

@SparkQA
Copy link

SparkQA commented Jan 9, 2016

Test build #49035 has finished for PR 10668 at commit bbd9c0d.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@ajbozarth
Copy link
Member Author

@srowen @tgravescs This is for the second half of SPARK-1832 that you reported if you want to take a look

@tgravescs
Copy link
Contributor

thanks for working on this. After seeing it I'm wondering if it would look better as a separate table just for the summary. Similar to the "Summary Metrics for X Completed Tasks" for a stage.

what do you guys think? copy @JoshRosen

@ajbozarth
Copy link
Member Author

@tgravescs I can put together an implementation of that to compare to, I don't know which would look better though, The stages summary doesn't have the same fields as the tables below it like this would, might look odd.

@ajbozarth
Copy link
Member Author

Here's a screenshot of @tgravescs summary table idea. [Note: this code is NOT committed] What do people think of this alternative? Opinions on how to improve it? I think we need to add a subhead for the original table, but I'm unsure of what it should say
screen shot 2016-01-11 at 4 27 11 pm

@tgravescs
Copy link
Contributor

personally I like this better because its always there and not moving when sorting.

One other reason I was going for a separate table is I filed another jira to show killed executors. I was thinking it might work as a nice summary for that where you could show active executors, inactive, as well as summaries across.

@ajbozarth
Copy link
Member Author

I just looked at that other PR and this will look great once that get's merged, I'll update the code to match the above screenshot

@SparkQA
Copy link

SparkQA commented Jan 12, 2016

Test build #49245 has finished for PR 10668 at commit 8b13783.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@ajbozarth
Copy link
Member Author

Do we want to wait for PR #10058 and then add an ACTIVE and DEAD row to the the table? Or Is this good to go?

#10058 seems stale, but I feel like the table looks off with just one row.

Also I think adding a header to the original table would look better but I personally can't think of what the header would say other than "Executors" which is already the page header, opinions?

@tgravescs
Copy link
Contributor

No we don't need to wait for that. I actually filed a new jira for what looks like the same thing.

You have "Totals for 5 Executors" on the top table so how about the bottom one we just put "Active Executors" since it doesn't show ones that are killed anyway.

<div class="span12">
<ul class="unstyled">
<li><strong>Memory:</strong>
{Utils.bytesToString(memUsed)} Used
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

memUsed and maxMem locals in this function aren't being used anymore so lets remove them.

@ajbozarth
Copy link
Member Author

screen shot 2016-01-14 at 3 10 10 pm

@SparkQA
Copy link

SparkQA commented Jan 15, 2016

Test build #49426 has finished for PR 10668 at commit f1cd333.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Jan 15, 2016

Test build #49423 has finished for PR 10668 at commit 4b5f7c7.

  • This patch passes all tests.
  • This patch does not merge cleanly.
  • This patch adds no public classes.

@tgravescs
Copy link
Contributor

+1, thanks @ajbozarth

@tgravescs
Copy link
Contributor

Oops sorry, it looks like it doesn't merge cleanly anymore. can you upmerge again.

@ajbozarth
Copy link
Member Author

The tests finished out of order, check the commit numbers. I thought that first too.

asfgit pushed a commit that referenced this pull request Mar 4, 2016
…otals Table

## What changes were proposed in this pull request?

Now that dead executors are shown in the executors table (#10058) the totals table is updated to include the separate totals for alive and dead executors as well as the current total, as originally discussed in #10668

## How was this patch tested?

Manually verified by running the Standalone Web UI in the latest Safari and Firefox ESR

Author: Alex Bozarth <ajbozart@us.ibm.com>

Closes #11381 from ajbozarth/spark13459.
roygao94 pushed a commit to roygao94/spark that referenced this pull request Mar 22, 2016
…otals Table

## What changes were proposed in this pull request?

Now that dead executors are shown in the executors table (apache#10058) the totals table is updated to include the separate totals for alive and dead executors as well as the current total, as originally discussed in apache#10668

## How was this patch tested?

Manually verified by running the Standalone Web UI in the latest Safari and Firefox ESR

Author: Alex Bozarth <ajbozart@us.ibm.com>

Closes apache#11381 from ajbozarth/spark13459.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants