diff options
| author | Hervé <dud225@users.noreply.github.com> | 2017-04-21 08:52:18 +0100 |
|---|---|---|
| committer | Sean Owen <sowen@cloudera.com> | 2017-04-21 08:52:18 +0100 |
| commit | 34767997e0c6cb28e1fac8cb650fa3511f260ca5 (patch) | |
| tree | 4d45d781abd2b92f421c1b4f5dad060a0895486a | |
| parent | e2b3d2367a563d4600d8d87b5317e71135c362f0 (diff) | |
| download | spark-34767997e0c6cb28e1fac8cb650fa3511f260ca5.tar.gz spark-34767997e0c6cb28e1fac8cb650fa3511f260ca5.tar.bz2 spark-34767997e0c6cb28e1fac8cb650fa3511f260ca5.zip | |
Small rewording about history server use case
Hello
PR #10991 removed the built-in history view from Spark Standalone, so the history server is no longer useful to Yarn or Mesos only.
Author: Hervé <dud225@users.noreply.github.com>
Closes #17709 from dud225/patch-1.
| -rw-r--r-- | docs/monitoring.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/monitoring.md b/docs/monitoring.md index da954385dc..3e577c5f36 100644 --- a/docs/monitoring.md +++ b/docs/monitoring.md @@ -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 |