From c48a08b7b95efee95ec1458982adfd9896231244 Mon Sep 17 00:00:00 2001 From: Kenjiro Nakayama Date: Sun, 6 Aug 2017 14:22:56 +0900 Subject: [PATCH] docs: fix tiny errors in monitoring spark app --- website/source/guides/spark/monitoring.html.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/source/guides/spark/monitoring.html.md b/website/source/guides/spark/monitoring.html.md index e4631a578..0b4ddce42 100644 --- a/website/source/guides/spark/monitoring.html.md +++ b/website/source/guides/spark/monitoring.html.md @@ -83,13 +83,13 @@ job "spark-history-server" { } ``` -The job file above can also be found [here](https://github.com/hashicorp/nomad/blob/f-terraform-config/terraform/examples/spark/spark-history-server.nomad). +The job file above can also be found [here](https://github.com/hashicorp/nomad/blob/master/terraform/examples/spark/spark-history-server-hdfs.nomad). To run the history server, first [deploy HDFS](/guides/spark/hdfs.html) and then create a directory in HDFS to store events: ```shell -$ hdfs dfs -mkdir /spark-events +$ hdfs dfs -fs hdfs://hdfs.service.consul:8020 -mkdir /spark-events ``` You can then deploy the history server with: @@ -101,7 +101,7 @@ $ nomad run spark-history-server-hdfs.nomad You can get the private IP for the history server with a Consul DNS lookup: ```shell -$ dig.spark-history.service.consul +$ dig spark-history.service.consul ``` Find the public IP that corresponds to the private IP returned by the `dig`