diff options
| author | Bryan Cutler <cutlerb@gmail.com> | 2016-05-04 14:29:54 -0700 |
|---|---|---|
| committer | Andrew Or <andrew@databricks.com> | 2016-05-04 14:29:54 -0700 |
| commit | cf2e9da612397233ae7bca0e9ce57309f16226b5 (patch) | |
| tree | 496c54cf5f861c8f9916671b91a415729e54e8bc /docs/monitoring.md | |
| parent | 0c00391f77359efdbf9dbd26d4c8186be8839922 (diff) | |
| download | spark-cf2e9da612397233ae7bca0e9ce57309f16226b5.tar.gz spark-cf2e9da612397233ae7bca0e9ce57309f16226b5.tar.bz2 spark-cf2e9da612397233ae7bca0e9ce57309f16226b5.zip | |
[SPARK-12299][CORE] Remove history serving functionality from Master
Remove history server functionality from standalone Master. Previously, the Master process rebuilt a SparkUI once the application was completed which sometimes caused problems, such as OOM, when the application event log is large (see SPARK-6270). Keeping this functionality out of the Master will help to simplify the process and increase stability.
Testing for this change included running core unit tests and manually running an application on a standalone cluster to verify that it completed successfully and that the Master UI functioned correctly. Also added 2 unit tests to verify killing an application and driver from MasterWebUI makes the correct request to the Master.
Author: Bryan Cutler <cutlerb@gmail.com>
Closes #10991 from BryanCutler/remove-history-master-SPARK-12299.
Diffstat (limited to 'docs/monitoring.md')
| -rw-r--r-- | docs/monitoring.md | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/docs/monitoring.md b/docs/monitoring.md index 697962ae3a..78a3470abf 100644 --- a/docs/monitoring.md +++ b/docs/monitoring.md @@ -27,11 +27,6 @@ in the UI to persisted storage. ## Viewing After the Fact -Spark's Standalone Mode cluster manager also has its own -[web UI](spark-standalone.html#monitoring-and-logging). If an application has logged events over -the course of its lifetime, then the Standalone master's web UI will automatically re-render the -application's UI after the application has finished. - 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. You can start the history server by executing: |