From 96fb894d4b33e293625fa92bbeccbbf5e688015e Mon Sep 17 00:00:00 2001
From: Tom Graves <tgraves@yahoo-inc.com>
Date: Fri, 15 Jan 2016 13:11:27 +0000
Subject: [PATCH] =?UTF-8?q?[SPARK-2930]=20clarify=20docs=20on=20using=20we?=
=?UTF-8?q?bhdfs=20with=20spark.yarn.access.nam=E2=80=A6?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
…enodes
Author: Tom Graves <tgraves@yahoo-inc.com>
Closes #10699 from tgravescs/SPARK-2930.
---
docs/running-on-yarn.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/running-on-yarn.md b/docs/running-on-yarn.md
index 06413f83c3..a148c867eb 100644
--- a/docs/running-on-yarn.md
+++ b/docs/running-on-yarn.md
@@ -260,10 +260,10 @@ If you need a reference to the proper location to put log files in the YARN so t
<td>(none)</td>
<td>
A comma-separated list of secure HDFS namenodes your Spark application is going to access. For
- example, <code>spark.yarn.access.namenodes=hdfs://nn1.com:8032,hdfs://nn2.com:8032</code>.
- The Spark application must have access to the namenodes listed and Kerberos must
- be properly configured to be able to access them (either in the same realm or in
- a trusted realm). Spark acquires security tokens for each of the namenodes so that
+ example, <code>spark.yarn.access.namenodes=hdfs://nn1.com:8032,hdfs://nn2.com:8032,
+ webhdfs://nn3.com:50070</code>. The Spark application must have access to the namenodes listed
+ and Kerberos must be properly configured to be able to access them (either in the same realm
+ or in a trusted realm). Spark acquires security tokens for each of the namenodes so that
the Spark application can access those remote HDFS clusters.
</td>
</tr>
--
GitLab