Skip to content

[DOC] Small rewording about history server use case #17709

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

[DOC] Small rewording about history server use case #17709

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/monitoring.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,8 @@ in the UI to persisted storage.

## Viewing After the Fact

If Spark is run on Mesos or YARN, it is still possible to construct the UI of an
application through Spark's history server, provided that the application's event logs exist.
It is still possible to construct the UI of an application through Spark's history server,
provided that the application's event logs exist.
You can start the history server by executing:

./sbin/start-history-server.sh
Expand Down