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-11272][Core][UI] Support importing and exporting event logs from HistoryServer web portal #9238

Closed
wants to merge 3 commits into from

Conversation

jerryshao
Copy link
Contributor

This patch helps user to easily download the event logs from HistoryServer, or upload other's log to debug and replay. Quite useful for user to seek help or identify problem for others. Here is the screenshot:

screen shot 2015-10-23 at 11 47 40 am

Please review. Thanks a lot.

@jerryshao jerryshao changed the title [SPARK-11272][Core] Support importing and exporting event logs from HistoryServer web portal [SPARK-11272][Core][UI] Support importing and exporting event logs from HistoryServer web portal Oct 23, 2015
@SparkQA
Copy link

SparkQA commented Oct 23, 2015

Test build #44197 has finished for PR 9238 at commit f92393f.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@jerryshao jerryshao changed the title [SPARK-11272][Core][UI] Support importing and exporting event logs from HistoryServer web portal [SPARK-11272][Core][UI][WIP] Support importing and exporting event logs from HistoryServer web portal Oct 23, 2015
@SparkQA
Copy link

SparkQA commented Oct 23, 2015

Test build #44221 has finished for PR 9238 at commit 6b20876.

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

@jerryshao jerryshao changed the title [SPARK-11272][Core][UI][WIP] Support importing and exporting event logs from HistoryServer web portal [SPARK-11272][Core][UI] Support importing and exporting event logs from HistoryServer web portal Oct 26, 2015
@jerryshao
Copy link
Contributor Author

Updated UI:

image

@SparkQA
Copy link

SparkQA commented Oct 26, 2015

Test build #44324 has finished for PR 9238 at commit af8b3cb.

  • This patch fails PySpark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@jerryshao
Copy link
Contributor Author

Jenkins, retest this please.

@SparkQA
Copy link

SparkQA commented Oct 26, 2015

Test build #44335 has finished for PR 9238 at commit af8b3cb.

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

* @throws SparkException if there's any exception read in the zip stream.
*/
@throws(classOf[SparkException])
def readEventLogs(zipStream: ZipInputStream): Unit
Copy link
Contributor

Choose a reason for hiding this comment

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

Rather than make this abstract, can you add a stub method which just goes throw new SparkException("Unsupported Feature"). That way any existing history provider will still load

@steveloughran
Copy link
Contributor

  1. Adding new abstract methods is going to break providers which use the current plugin point. Adding base implementations which throw an "unsupported" exception would be better.
  2. If there was also a hasFeature method to enumerate/probe for features, the UI could adapt and skip showing UI features which aren't implemented
  3. You can bring up a history server in the test suite. This will let you test that the actual POST operation works, If you look at the SPARK-1537 publisher tests you can see me doing this for the GET side of things.

@andrewor14
Copy link
Contributor

The download functionality is super cool, but the import part has somewhat confusing semantics. The history server is supposed to dynamically sync all logs in a specific directory. With this patch you can have logs that you uploaded but no longer exist, and the original logs don't have to be from the same path. Above all this seems like a rather niche use case.

@andrewor14
Copy link
Contributor

@jerryshao would you mind closing this PR and maybe re-opening one that only supports the download functionality?

@jerryshao
Copy link
Contributor Author

OK, I see. I will close this PR, thanks a lot for your comments.

@jerryshao jerryshao closed this Dec 15, 2015
asfgit pushed a commit that referenced this pull request Oct 13, 2016
…toryServer UI

## What changes were proposed in this pull request?

This is a reworked PR based on feedback in #9238 after it was closed and not reopened. As suggested in that PR I've only added the download feature. This functionality already exists in the api and this allows easier access to download event logs to share with others.

I've attached a screenshot of the committed version, but I will also include alternate options with screen shots in the comments below. I'm personally not sure which option is best.

## How was this patch tested?

Manual testing

![screen shot 2016-10-07 at 6 11 12 pm](https://cloud.githubusercontent.com/assets/13952758/19209213/832fe48e-8cba-11e6-9840-749b1be4d399.png)

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

Closes #15400 from ajbozarth/spark11272.
uzadude pushed a commit to uzadude/spark that referenced this pull request Jan 27, 2017
…toryServer UI

## What changes were proposed in this pull request?

This is a reworked PR based on feedback in apache#9238 after it was closed and not reopened. As suggested in that PR I've only added the download feature. This functionality already exists in the api and this allows easier access to download event logs to share with others.

I've attached a screenshot of the committed version, but I will also include alternate options with screen shots in the comments below. I'm personally not sure which option is best.

## How was this patch tested?

Manual testing

![screen shot 2016-10-07 at 6 11 12 pm](https://cloud.githubusercontent.com/assets/13952758/19209213/832fe48e-8cba-11e6-9840-749b1be4d399.png)

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

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