Skip to content

Conversation

@shivusondur
Copy link
Contributor

@shivusondur shivusondur commented Sep 27, 2018

What changes were proposed in this pull request?

Currently, in History spark UI, the number of Jobs in the jobs page and "spark.ui.retainedJobs" value in
the Environment page is not matching.
So we need to override the spark properties from the History spark-default.conf properties, which will match the number of jobs showing in jobs page and value of "spark.ui.retainedJobs" in the Environment Page.
Same applies to other History specific parameters such as "spark.ui.retainedTasks" etc.

How was this patch tested?

Tested in master branch

  1. In the spark-default.conf mentioned the spark.ui.retainedJobs=200
  2. In spark shell command mentioned the 100 like below command
    "spark-shell --master yarn --conf spark.ui.retainedJobs=100"

Attached the test result screenshot
spark.ui.retainedJobs is showing specific to historypage
image

Now the total jobs showing and the spark.ui,retainedJobs value in the Environment page are matching.

46128573-87b92f00-c251-11e8-926c-030d86e15ad5

@shivusondur shivusondur changed the title [SPARK-25550] [Spark Job History] Environment Page of Spark Job History UI showing wrong value for spark.ui.retainedJobs [SPARK-25550] [WEBUI] Environment Page of Spark Job History UI showing wrong value for spark.ui.retainedJobs Sep 27, 2018
@shivusondur shivusondur changed the title [SPARK-25550] [WEBUI] Environment Page of Spark Job History UI showing wrong value for spark.ui.retainedJobs [WIP]Environment Page of Spark Job History UI showing wrong value for spark.ui.retainedJobs Sep 27, 2018
@shivusondur shivusondur reopened this Sep 27, 2018
@shivusondur shivusondur changed the title [WIP]Environment Page of Spark Job History UI showing wrong value for spark.ui.retainedJobs [SPARK-25550][WEBUI]Environment Page of Spark Job History UI showing wrong value for spark.ui.retainedJobs Sep 27, 2018
@shivusondur
Copy link
Contributor Author

@vanzin Please review this patch.

@vanzin
Copy link
Contributor

vanzin commented Oct 4, 2018

Hmmm, not sure about this. That page is supposed to show the application's configuration, not the history server configuration.

If you want to add a new page to show SHS-specific configs, then that would be a better change. Otherwise this can be misleading. e.g. knowing the original config value can help someone debug things if the app ran into OOM issues.

Otherwise I don't think this should go in.

@shivusondur
Copy link
Contributor Author

shivusondur commented Oct 9, 2018

@vanzin
I modified according to your suggestion and updated the code.
Now History properties will come as seperate tab in the EnvironmentPage as shown below snap.

History UI
screenshot from 2018-10-09 11-47-07

screenshot from 2018-10-09 12-03-12

Only in the history UI, History Properties will be displayed. In live UI history properties won't be there

Live UI
screenshot from 2018-10-09 12-00-11

@vanzin
Copy link
Contributor

vanzin commented Oct 15, 2018

That has the same problem as before. This page is for the application, not for the history server. It should not show different things just because you're looking at it in the history server.

If you want to expose the SHS config you have to do it in a separate page that is not part of the application-specific UI. And then you have to be careful with what you show there, since the SHS config may have sensitive information that users should not see.

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@srowen srowen mentioned this pull request Oct 24, 2018
@asfgit asfgit closed this in 65c653f Oct 25, 2018
zifeif2 pushed a commit to zifeif2/spark that referenced this pull request Nov 22, 2025
Closes apache#22567
Closes apache#18457
Closes apache#21517
Closes apache#21858
Closes apache#22383
Closes apache#19219
Closes apache#22401
Closes apache#22811
Closes apache#20405
Closes apache#21933

Closes apache#22819 from srowen/ClosePRs.

Authored-by: Sean Owen <sean.owen@databricks.com>
Signed-off-by: Sean Owen <sean.owen@databricks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants